-
Notifications
You must be signed in to change notification settings - Fork 71
Description
Hello everyone
According to this Apple Technote, the UIScene life cycle will be required in the next major iOS release following iOS 26. However, the current SDK documentation does not provide guidance on the proper way to adopt it with mParticle.
At the moment, our integration relies on the UIApplication Delegate Proxy to intercept key application life-cycle events and handle features such as deep link navigation and user activities. Once the app implements a SceneDelegate, many of these events are handled there instead of in the UIApplication.delegate, meaning they are no longer automatically forwarded to the mParticle SDK.
Additionally, several UIApplicationDelegate methods — including application(_:open:options:) — are now marked as deprecated, along with other key entry points.
Questions
Given these upcoming changes, I’d like to clarify a few points:
-
Integration approach
What’s the correct way to integrate mParticle using the UIScene life cycle?- Is there any documentation or example for UIScene-based setups?
- Should we disable the delegate proxy and manually forward each event to the SDK?
-
Handling launch options
Inapplication(_:didFinishLaunchingWithOptions:), thelaunchOptionsparameter becomesnilafter adoptingSceneDelegate.
Instead, that data is now available inscene(_:willConnectTo:options:)underconnectionOptions.- If needed, how should this data be forwarded to mParticle to ensure proper handling of app launches from shortcuts, push notifications, or similar entry points?
-
API alignment
UISceneDelegatemethods often provide different types and data structures.- Will the SDK be updated to support the UIScene life cycle natively or to match the
UISceneDelegateAPI? - If not, is there recommended guidance on how to forward SceneDelegate events without losing contextual information?
- Will the SDK be updated to support the UIScene life cycle natively or to match the
This change in Apple’s app life-cycle model will soon affect all iOS apps, so having an official recommendation or migration guide from mParticle would be really helpful for developers preparing for iOS 27 and beyond.