-
Notifications
You must be signed in to change notification settings - Fork 194
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
Crash in [AMPTrackingOptions shouldTrackPlatform]
when initializing Amplitude
#498
Comments
Hi @terribleben I'm wondering if this may be a concurrent access issue on |
Sure thing - I pulled out an example from our Sentry logs. It contains Thanks for your response!
|
Thanks! It does not appear to be a threading issue as Amplitude is only accessed on thread 6. Please let me know if you have any additional information about how to reproduce the issue, otherwise I'll continue to look on my end. |
Could you please see if #499 fixes the crash? |
Sounds good - I'll patch in this change. Since the crash doesn't repro reliably, I can't give a fast/firm answer unless I happen to catch it. The change looks relatively safe, so we can try releasing to a small percent of our users and see if it still shows up; but it might be several days before I can do a production release. Will let you know! |
Thanks @terribleben - we'll get this merged into main but I'll wait to hear back from you before releasing. |
Can confirm that we're no longer seeing this issue in production after patching the fix. Thanks! |
This should be released in 8.19.3 |
Expected Behavior
The app should launch without crashing.
Current Behavior
The app crashed while attempting to run
Amplitude startNewSession:
downstream ofinitializeApiKey:
at boot time.Here's a screenshot of what we're seeing:
Environment
More info
We see about 15 occurrences of this crash per 24h period in our production app. Here are the Sentry analytics about the distribution of the crash:
Full stack trace
The text was updated successfully, but these errors were encountered: