-
Notifications
You must be signed in to change notification settings - Fork 195
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Error when deep linking on app boot #226
Comments
I got the same issue. |
Any updates here? |
when debug, i found they has Assert here http://prntscr.com/v9woko, and when you open with deeplink, the url is handled by launchOptions[UIApplicationLaunchOptionsURLKey] in http://prntscr.com/v9wpqi has NSURL type, so, it doesn't match with type that can be serialized. |
Seems like it was fixed in the iOS repo: Hopefully we'll get a new release of the pod and the npm soon 🤞 |
I've struggled with this issue on 1.3.1 version. After upgrading to 1.3.2 everything works fine 🎉 |
Hi Segment,
I'm seeing an error on a deep linking cold boot:
This occurs on the simulator when I boot the app with a command like:
Notably, this doesn't occur when using universal links, and doing something like
This error is most likely a bug within the Segment RNAnalytics library as it only happens when using the
trackApplicationLifecycleEvents
flag during init, which causes a crash in the library in this line when it tries to send the_bridge.launchOptions
since it seems to have trouble dealing with UIApplicationLaunchOptionsURLKey that our deep link opens with. Hence the error 'key url is a NSURL and can't be serialized for delivery.'If we disable the
trackApplicationLifecycleEvents
, it doesn't happen, but I'd like to use that.Any thoughts here? I can provide more info too if necessary.
relevant packages:
The text was updated successfully, but these errors were encountered: