{"id":6567,"date":"2019-12-12T06:17:15","date_gmt":"2019-12-12T06:17:15","guid":{"rendered":"https:\/\/9series-blog.staging9.com\/?p=6567"},"modified":"2026-03-12T08:19:50","modified_gmt":"2026-03-12T08:19:50","slug":"build-share-extension-ios-using-swift-4-0","status":"publish","type":"post","link":"https:\/\/www.9series.com\/blog\/build-share-extension-ios-using-swift-4-0\/","title":{"rendered":"How to Build a Share Extension in iOS Using Swift 4.0"},"content":{"rendered":"

\"Share<\/a><\/p>\n

In our earlier post, we explained how to build a Share Extension using Swift 3.0. In this guide, we will walk through the same process using Swift 4.0.<\/span>\u00a0<\/span><\/p>\n

The main\u00a0objective\u00a0of building a Share Extension is to enable an app to save a URL as rich content and configure custom options directly from the iOS share sheet. A Share Extension allows your app icon to appear in the system\u00a0share\u00a0menu and handle content shared by the user without switching manually between apps.<\/span>\u00a0<\/span><\/p>\n

Building a Share Extension in iOS using Swift is straightforward and helps simplify content sharing workflows in mobile app development.<\/span>\u00a0<\/span><\/p>\n

\u00a0<\/span><\/p>\n

Laying the Groundwork<\/span><\/b>\u00a0<\/span><\/h2>\n

You can either:<\/span>\u00a0<\/span><\/p>\n

    \n
  • Create a new Xcode project<\/span>\u00a0<\/span><\/li>\n<\/ul>\n
      \n
    • Open an existing project where you want to add the Share Extension<\/span>\u00a0<\/span><\/li>\n<\/ul>\n

      Step 1: Add a Share Extension Target<\/span><\/b>\u00a0<\/span><\/p>\n

        \n
      1. Go to File > New > Target<\/span>\u00a0<\/span><\/li>\n<\/ol>\n
          \n
        1. Select the iOS tab<\/span>\u00a0<\/span><\/li>\n<\/ol>\n
            \n
          1. Choose Share Extension<\/span>\u00a0<\/span><\/li>\n<\/ol>\n
              \n
            1. Click Next and rename it as\u00a0required<\/span>\u00a0<\/span><\/li>\n<\/ol>\n

              To test your extension properly, activate the\u00a0option\u00a0to run the app using a browser such as Safari. This ensures smoother testing and responsiveness.<\/span>\u00a0<\/span><\/p>\n

              Once set up:<\/span>\u00a0<\/span><\/p>\n

                \n
              • Run the project<\/span>\u00a0<\/span><\/li>\n<\/ul>\n
                  \n
                • Open Safari<\/span>\u00a0<\/span><\/li>\n<\/ul>\n
                    \n
                  • Tap the Share icon<\/span>\u00a0<\/span><\/li>\n<\/ul>\n
                      \n
                    • Look for your extension name<\/span>\u00a0<\/span><\/li>\n<\/ul>\n

                      If it does not appear, tap the More button and enable it.<\/span>\u00a0<\/span><\/p>\n

                      When you select your extension, it will load the default implementation associated with\u00a0SLComposeServiceViewController.<\/span>\u00a0<\/span><\/p>\n

                      \u00a0<\/span><\/p>\n

                      Fetching the URL<\/span><\/b>\u00a0<\/span><\/h2>\n

                      Once enabled, the share sheet automatically retrieves certain information such as:<\/span>\u00a0<\/span><\/p>\n

                        \n
                      • Page title<\/span>\u00a0<\/span><\/li>\n<\/ul>\n
                          \n
                        • Basic metadata<\/span>\u00a0<\/span><\/li>\n<\/ul>\n

                          However, for advanced use cases, you may need\u00a0additional\u00a0details from the webpage. To achieve this, you can run a JavaScript file to parse the document and extract more information.<\/span>\u00a0<\/span><\/p>\n

                          Step 2: Create a JavaScript File<\/span><\/b>\u00a0<\/span><\/p>\n

                            \n
                          1. Go to your Extensions folder in Xcode<\/span>\u00a0<\/span><\/li>\n<\/ol>\n
                              \n
                            1. Select New File<\/span>\u00a0<\/span><\/li>\n<\/ol>\n
                                \n
                              1. Under the Other tab, choose Empty<\/span>\u00a0<\/span><\/li>\n<\/ol>\n
                                  \n
                                1. Rename it to GetURL.js<\/span>\u00a0<\/span><\/li>\n<\/ol>\n

                                  Step 3: Update\u00a0Info.plist<\/span><\/b>\u00a0<\/span><\/p>\n

                                  Edit the extension\u2019s\u00a0Info.plist\u00a0file and:<\/span>\u00a0<\/span><\/p>\n

                                    \n
                                  • Add\u00a0NSExtensionJavascriptProcessingFile\u00a0under\u00a0NSExtensionAttributes<\/span>\u00a0<\/span><\/li>\n<\/ul>\n
                                      \n
                                    • Set its value to\u00a0GetURL\u00a0without the .js\u00a0extension<\/span>\u00a0<\/span><\/li>\n<\/ul>\n
                                        \n
                                      • Add\u00a0NSExtensionActivationSupportsWebURLWithMaxCount\u00a0under\u00a0NSExtensionActivationRule<\/span>\u00a0<\/span><\/li>\n<\/ul>\n

                                        The system looks for an object named\u00a0ExtensionProcessingJS\u00a0at runtime inside the JavaScript file.<\/span>\u00a0<\/span><\/p>\n

                                        For detailed implementation references, consult the official documentation from Apple.<\/span>\u00a0<\/span><\/p>\n

                                        Step 4: Retrieve Data in Swift<\/span><\/b>\u00a0<\/span><\/p>\n

                                        In\u00a0ShareViewController.swift:<\/span>\u00a0<\/span><\/p>\n

                                          \n
                                        • Import\u00a0kUTTypePropertyList<\/span>\u00a0<\/span><\/li>\n<\/ul>\n
                                            \n
                                          • Retrieve the processed data inside\u00a0viewDidLoad<\/span>\u00a0<\/span><\/li>\n<\/ul>\n

                                            When you run the extension, the URL will now print in the console.<\/span>\u00a0<\/span><\/p>\n

                                            \u00a0<\/span><\/p>\n

                                            Customizing and Adding Configuration Cells<\/span><\/b>\u00a0<\/span><\/h2>\n

                                            You can enhance the Share Extension by adding configuration items at the bottom of the share sheet.<\/span>\u00a0<\/span><\/p>\n

                                            Configuration items allow users to:<\/span>\u00a0<\/span><\/p>\n

                                              \n
                                            • Select categories or decks<\/span>\u00a0<\/span><\/li>\n<\/ul>\n
                                                \n
                                              • Save preferences<\/span>\u00a0<\/span><\/li>\n<\/ul>\n
                                                  \n
                                                • Trigger\u00a0additional\u00a0JavaScript processing<\/span>\u00a0<\/span><\/li>\n<\/ul>\n

                                                  When the Share Extension target is created, it includes\u00a0boilerplate\u00a0code that supports\u00a0SLComposeSheetConfigurationItem.<\/span>\u00a0<\/span><\/p>\n

                                                  Step 5: Create a Model<\/span><\/b>\u00a0<\/span><\/p>\n

                                                  Create a simple model file called:<\/span>\u00a0<\/span><\/p>\n

                                                  Deck.swift<\/span>\u00a0<\/span><\/p>\n

                                                  This model will help pass selected data between view controllers.<\/span>\u00a0<\/span><\/p>\n

                                                  \u00a0<\/span><\/p>\n

                                                  Creating a Table View for Selection<\/span><\/b>\u00a0<\/span><\/h2>\n

                                                  To display selectable options:<\/span>\u00a0<\/span><\/p>\n

                                                    \n
                                                  1. Create a new\u00a0UIViewController\u00a0file<\/span>\u00a0<\/span><\/li>\n<\/ol>\n
                                                      \n
                                                    1. Name it\u00a0ShareSelectViewController.swift<\/span>\u00a0<\/span><\/li>\n<\/ol>\n
                                                        \n
                                                      1. Add a table view property<\/span>\u00a0<\/span><\/li>\n<\/ol>\n
                                                          \n
                                                        1. Populate it with dummy data<\/span>\u00a0<\/span><\/li>\n<\/ol>\n
                                                            \n
                                                          1. Add it inside\u00a0viewDidLoad<\/span>\u00a0<\/span><\/li>\n<\/ol>\n

                                                            Next, instantiate\u00a0ShareSelectViewController\u00a0inside the\u00a0tapHandler\u00a0of your configuration item.<\/span>\u00a0<\/span><\/p>\n

                                                            Run the app after each update to ensure proper mobile app testing. When tapping the configuration cell, the table view should appear with dummy data.<\/span>\u00a0<\/span><\/p>\n

                                                            \u00a0<\/span><\/p>\n

                                                            Updating the Selected Deck<\/span><\/b>\u00a0<\/span><\/h2>\n

                                                            Initially, the configuration cell may display a default label such as “Deck Title”.<\/span>\u00a0<\/span><\/p>\n

                                                            To update it dynamically:<\/span>\u00a0<\/span><\/p>\n

                                                              \n
                                                            1. Create a property to store the selected deck<\/span>\u00a0<\/span><\/li>\n<\/ol>\n
                                                                \n
                                                              1. Set a default value<\/span>\u00a0<\/span><\/li>\n<\/ol>\n
                                                                  \n
                                                                1. Update it inside\u00a0configurationItems()<\/span>\u00a0<\/span><\/li>\n<\/ol>\n

                                                                  To handle navigation:<\/span>\u00a0<\/span><\/p>\n

                                                                    \n
                                                                  • Create a protocol for delegation<\/span>\u00a0<\/span><\/li>\n<\/ul>\n
                                                                      \n
                                                                    • Conform\u00a0ShareViewController\u00a0to that protocol<\/span>\u00a0<\/span><\/li>\n<\/ul>\n
                                                                        \n
                                                                      • Set the delegate to self in\u00a0ShareSelectViewController<\/span>\u00a0<\/span><\/li>\n<\/ul>\n

                                                                        After implementing delegation and running the app again, the selected deck updates automatically in the configuration section.<\/span>\u00a0<\/span><\/p>\n

                                                                        \u00a0<\/span><\/p>\n

                                                                        Sending Information to the Server<\/span><\/b>\u00a0<\/span><\/h2>\n

                                                                        Once all data is collected, the\u00a0final step\u00a0is sending it to the server or sharing it with the main app.<\/span>\u00a0<\/span><\/p>\n

                                                                        You can use:<\/span>\u00a0<\/span><\/p>\n

                                                                          \n
                                                                        • NSURLSession\u00a0to post data to your backend server<\/span>\u00a0<\/span><\/li>\n<\/ul>\n
                                                                            \n
                                                                          • App Groups to share data between the extension and the main app<\/span>\u00a0<\/span><\/li>\n<\/ul>\n
                                                                              \n
                                                                            • NSUserDefaults\u00a0to store and retrieve shared data<\/span>\u00a0<\/span><\/li>\n<\/ul>\n

                                                                              Replace dummy data with actual configured data before production deployment.<\/span>\u00a0<\/span><\/p>\n

                                                                              Additional Customizations<\/span><\/b>\u00a0<\/span><\/h3>\n
                                                                                \n
                                                                              • Change the extension icon through project settings<\/span>\u00a0<\/span><\/li>\n<\/ul>\n
                                                                                  \n
                                                                                • Modify the Display Name in extension settings to update its name in the share sheet<\/span>\u00a0<\/span><\/li>\n<\/ul>\n

                                                                                  \u00a0<\/span><\/p>\n

                                                                                  Conclusion<\/span><\/b>\u00a0<\/span><\/h2>\n

                                                                                  Building a Share Extension in iOS using Swift 4.0 allows developers to enhance content sharing and improve user experience. By integrating JavaScript processing,\u00a0configuration\u00a0cells, table views, and server communication, you can create a powerful and\u00a0user friendly\u00a0sharing workflow.<\/span>\u00a0<\/span><\/p>\n

                                                                                  A well implemented Share Extension:<\/span>\u00a0<\/span><\/p>\n

                                                                                    \n
                                                                                  • Simplifies cross app interaction<\/span>\u00a0<\/span><\/li>\n<\/ul>\n
                                                                                      \n
                                                                                    • Enhances content handling<\/span>\u00a0<\/span><\/li>\n<\/ul>\n
                                                                                        \n
                                                                                      • Improves productivity<\/span>\u00a0<\/span><\/li>\n<\/ul>\n
                                                                                          \n
                                                                                        • Strengthens user engagement<\/span>\u00a0<\/span><\/li>\n<\/ul>\n

                                                                                          If you are planning to enhance your iOS app with custom Share Extensions, following this structured approach will ensure smooth integration and scalability.<\/span>\u00a0<\/span><\/p>\n

                                                                                          For\u00a0implementation\u00a0examples and code references, you can explore official developer documentation and community supported repositories for further guidance.<\/span>\u00a0<\/span><\/p>\n","protected":false},"excerpt":{"rendered":"

                                                                                          In our earlier post, we explained how to build a Share Extension using Swift 3.0. In this guide, we will walk through the same process using Swift 4.0.\u00a0 The main\u00a0objective\u00a0of…<\/p>\n","protected":false},"author":1,"featured_media":6568,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"dsgo_overlay_header":false,"dsgo_overlay_header_text_color":"","dsgo_overlay_skip_top_bar":false,"_designsetgo_exclude_llms":false,"footnotes":""},"categories":[1439],"tags":[2408,1528,2204,1713,2474,2475,2476],"class_list":["post-6567","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-ios","tag-android-ios-developers","tag-apple","tag-ios-development-services","tag-mobile-app-development","tag-share-extension","tag-swift-4-0","tag-swift-programming"],"_links":{"self":[{"href":"https:\/\/www.9series.com\/blog\/wp-json\/wp\/v2\/posts\/6567","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.9series.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.9series.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.9series.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.9series.com\/blog\/wp-json\/wp\/v2\/comments?post=6567"}],"version-history":[{"count":2,"href":"https:\/\/www.9series.com\/blog\/wp-json\/wp\/v2\/posts\/6567\/revisions"}],"predecessor-version":[{"id":6912,"href":"https:\/\/www.9series.com\/blog\/wp-json\/wp\/v2\/posts\/6567\/revisions\/6912"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.9series.com\/blog\/wp-json\/wp\/v2\/media\/6568"}],"wp:attachment":[{"href":"https:\/\/www.9series.com\/blog\/wp-json\/wp\/v2\/media?parent=6567"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.9series.com\/blog\/wp-json\/wp\/v2\/categories?post=6567"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.9series.com\/blog\/wp-json\/wp\/v2\/tags?post=6567"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}