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
@arthurchenjs From the first glance the crash looks like a concurrency issue in GULHeartbeatDateStorage . Could you please provide the following information to help us investigate the issue:
Call stacks for other threads (you may consider removing replacing the call stack parts that you are not comfortable posting here)
Is Firebase used by an app extension?
EXC_BREAKPOINT may indicate a crash under debugger. If it is the case, the crash may be unrelated to the app code. Do you have an idea where the crash came from?
A sample app to reproduce the crash would really speed up the investigation. Do you think you can provide it?
Firebase is not used in extension
This is an online user, and our mokey autotest only reappears once
We can't provide sample app yet copy-MYXJ-2020-03-12-211822.crash.txt
@arthurchenjs The crash log indicates that the app was killed due to unresponsive main thread. It looks like the app was pretty "busy" at the moment of the crash. The PR #5114 moves file system operations of the main thread (which was a mistake), so Firebase will contribute less to the main thread load.
[REQUIRED] Step 1: Describe your environment
CocoaPods
(select one)[REQUIRED] Step 2: Describe the problem
Steps to reproduce:
user crash
The text was updated successfully, but these errors were encountered: