<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>app extension on Madison&#39;s Blog</title>
    <link>https://solarana.dev/tags/app-extension/</link>
    <description>Recent content in app extension on Madison&#39;s Blog</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-us</language>
    <lastBuildDate>Mon, 19 Dec 2022 08:40:00 -0500</lastBuildDate><atom:link href="https://solarana.dev/tags/app-extension/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Handling App Extension Code</title>
      <link>https://solarana.dev/2022/12/19/handling-app-extension-code/</link>
      <pubDate>Mon, 19 Dec 2022 08:40:00 -0500</pubDate>
      
      <guid>https://solarana.dev/2022/12/19/handling-app-extension-code/</guid>
      <description>Over the past couple of years, Apple has been slowly increasing the number and kinds of App Extensions one can associate with their applications. As such, reusing code between a main application and an extension is somewhat desireable.
At the most basic level, adding a logic branch to a path is crude, but effective:
if ([NSBundle.mainBundle.bundlePath hasSuffix:@&amp;#34;.appex&amp;#34;]) { // Do app extension stuff } else { // Do main app stuff } Unfortunately, this does not handle the case where the main application branch references APIs that are unavailable in app extensions.</description>
    </item>
    
  </channel>
</rss>
