You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Two targets on the same code base with different configurations, the one that's in production is having a critical and strange issue:
App is running
User clicks on a deeplink from outside the app
App is triggered and is opened and one of two things happen:
On the test target, initSessionWithLaunchOptions:andRegisterDeepLinkHandler: callback is being called immediately as expected as a response to clicking the link.
On the production target the callback back isn't called until the app goes to background (for example: opening the iOS notification screen).
because the app is refocused from the link, and because the deeplink is called, only not in the right time, the configuration seems to be ok.
One thing I've noticed is that in regards to the app delegate, on the production target the deep link triggers:
(BOOL)application:(UIApplication *)app openURL:(NSURL *)url options:(NSDictionary<NSString *,id> *)options {
While the other target's deeplink triggers
Are you using the same URL scheme and applink domains defined correctly in both configurations?
Check that the URL scheme defined in your Info.plist is correct in both, and that your associated domains are set up in your app's capabilities section.
* Updated our URI scheme filter that finds a URI scheme for the partner's app.
* Updated the docs to clarify that the partner's app URI should be the first URI.
* This clarifies issue #825
Two targets on the same code base with different configurations, the one that's in production is having a critical and strange issue:
because the app is refocused from the link, and because the deeplink is called, only not in the right time, the configuration seems to be ok.
One thing I've noticed is that in regards to the app delegate, on the production target the deep link triggers:
While the other target's deeplink triggers
The text was updated successfully, but these errors were encountered: