lahaiheart.blogg.se - Objective c to swift migration

If the extension builds without issues, you do not have anything to do!

Please click here to open the rich push setup guide which will walk you through integrating the extension, and come back here once done.

The extension is available on Swift Package Manager, CocoaPods and Carthage. Note: If your extension code is written in Objective-C and uses BAENotificationServiceExtension, please use the Objective-C version of the extension. Now, we have to add it back! Adding the new BatchExtension using a package manager Be careful, as you might have multiple script phases.īatchExtension has now been fully removed from your project. Now, go in your main target's Build Steps and find the Run Script phase that refences a script which path contains amework/strip-frameworks.sh. Xcode should have automatically removed the framework reference from the Link Binary With Libraries and Embed Frameworks build steps. When asked what to do with the deletion, pick Move To Trash. In order to remove the framework, simply find it in the Project Navigator (which is the first tab of the left sidebar), and delete it: Since BatchExtension has never been distributed on a package manager, you had to copy it in your project and add a script phase.

Update your code to match the new API signatures, if needed.

Add the new one using a package manager.

Remove the old BatchExtension framework.

Migrating to the new BatchExtension is done in three steps: The only way to integrate BatchExtension in your application from now on is using the source.įortunately, package managers make this easy to deal with! This marks the end of the binary distribution of BatchExtension, which used to be bundled with the SDK downloads.

(Objective-C version, should only be used if you cannot use the Swift one).

With the 1.16 release, BatchExtension has been rewritten and open-source in two repositories: Migrating from the older binary BatchExtension If your app targets an older version of iOS, please downgrade to 1.15. iOS minimum versionīatch 1.16 requires iOS 10.0 or higher. This migration guide will help you update your implementation. Batch 1.16 comes with a number of changes regarding the distribution of the SDK and it's extension counterpart.