-
Notifications
You must be signed in to change notification settings - Fork 47
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
Storage.swift: + 253 : Thread Issue #91
Comments
Hi ! Can you provide some input like calling code when the crash occurs to check ? Regards |
Here is the stack for the crash, don't know if you can find something in it: `Hardware Model: iPad7,11 Date/Time: 2020-07-31 06:25:12.4569 +0200 Exception Type: EXC_BREAKPOINT (SIGTRAP) Thread 0 name: Thread 1 name: Thread 2 name: Thread 3 name: Thread 4 name: Thread 5 name: Thread 6: Thread 7: Thread 8 name: Thread 9 name: Thread 10 name: Thread 11 name: Thread 12: Thread 9 crashed with ARM Thread State (64-bit): |
I can see crash was caused by Thread 9, and the stack have not reference to our code no ? |
The crash is on thread 9, and the you open in Xcode you see the other thread that are concurrent. 11 : |
OK so just to have more information can you provide your calling code to check how the SDK is used ? Also, can you say if you have multithreading usage with same tracker instance ? Many thanks |
To unlock, we will add catch block to avoid unexpected crash in the next release |
This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 5 days |
The 2.19.0 SDK version is available and fix this issue Many thanks for your report ! |
This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 5 days |
Hey,
We have the following crash in our app :
![Screen Shot 2020-08-06 at 10 53 37](https://user-images.githubusercontent.com/13964794/89512255-3e35b580-d7d3-11ea-883f-1aeafc206f19.png)
maybe a try catch will do the trick ?
thank you
The text was updated successfully, but these errors were encountered: