-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
Occasionally crashes when starting the app #13843
Comments
I couldn't figure out how to label this issue, so I've labeled it for a human to triage. Hang tight. |
Hi @zhangbokika, could you provide the full stack trace of your crash? |
I have the same crash, archived with xcode 16. Podfile lock
|
@rizafran Thank you very much for your reply, # Crashlytics - Stack trace Application: xxxPlatform: appleVersion: 4.9.3 (302071959)Issue: 13e07f0782e5a707fe366c8d3d96727bSession: e40b2b89f70c49f48f2f93ae71b15fea_DNE_0_v2Date: Tue Oct 08 2024 07:30:03 GMT+0800Fatal Exception: NSGenericException ConfigurationStorage.sync.queue Crashed: com.google.firebase.crashlytics.ios.exception startSDK com.apple.root.default-qos com.google.GDTCORFlatFileStorage com.apple.uikit.eventfetch-thread com.apple.root.default-qos Thread Thread Thread com.apple.root.default-qos Thread com.google.firebase.crashlytics.MachExceptionServer com.apple.root.default-qos com.apple.NSURLConnectionLoader JavaScriptCore libpas scavenger Thread extension-process-background-queue APAPIThread APEventThread trust com.apple.root.default-qos Thread com.apple.root.default-qos Thread Thread com.apple.CoreMotion.MotionThread |
Have you solved the problem |
I have the same problem with me. The stack trace from my app is as follows:
|
I'm having the same problem with my project and don't know what to do about it |
My crash log is as followsApplication: our appPlatform: appleVersion: 1.2.4 (1.2.4.1)Issue: 13e07f0782e5a707fe366c8d3d96727bSession: 52c6e529f4a745f6b2c5d19ae2a62e03_DNE_0_v2Date: Wed Oct 16 2024 22:49:50 GMT+0800 (中国标准时间)Fatal Exception: NSGenericException |
We have had crashes in our app with callstacks similar to HyunjoonKo and qinfendezhou (i.e. without the two FirebasePerformance 0x18050 __InstrumentDataTaskWithRequestCompletionHandler_block_invoke lines that are present in the OP's callstack). We tracked it down to the Liftoff/Vungle ad network. We have been informed that updating our Vungle SDK to 7.4.2 should fix it (https://developers.google.com/admob/ios/mediation/liftoff-monetize / https://support.vungle.com/hc/en-us/articles/15718672681883-Download-Vungle-SDK-for-iOS "Added guards to fix sporadic race condition issues when the SDK initializes"). We haven't rolled out that fix so we don't know for sure that will fix it. I suspect that this is not the explanation for everyone's crashes, but may be useful information for some. Edit: We have now deployed the Vungle SDK update to 7.4.2 and I can confirm that it has fixed this crash for us. |
+1 |
1 similar comment
+1 |
Is anyone still experiencing this issue without Vungle SDK being involved in their project? |
We are also experiencing this issue. Currently, we are using Firebase 11.5.0, and this crash accounts for 40% of our total crashes. Additionally, we are using VungleSDK: VungleAds, version 4.7.2.
|
I believe the crash we are experiencing is also related to this, here is the stack trace:
|
Actually @kseniyastar, it would seem our crashes come from the Segment SDK (see here) |
Description
Occasionally crashes when starting the app
Reproducing the issue
No response
Firebase SDK Version
17.6.1 18.0
Xcode Version
15.4
Installation Method
CocoaPods
Firebase Product(s)
Crashlytics
Targeted Platforms
iOS
Relevant Log Output
If using Swift Package Manager, the project's Package.resolved
No response
If using CocoaPods, the project's Podfile.lock
The text was updated successfully, but these errors were encountered: