-
Notifications
You must be signed in to change notification settings - Fork 1.6k
Firebase crash : com.google.fira.worker #673
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
Comments
Tracked internally at b/72036686 |
@flashwade03 looks like there are some missing symbols in your stack trace. Can you symbolicate it fully? |
Here is my full stack trace downloaded from crashlytics. Thanks! |
@flashwade03 How often does it happen? I weren't able to reproduce this issue. Could you provide some additional instructions for us to reproduce the crash? |
@flashwade03 : you said it happened when users quit the app. Does it mean completely closing the app or putting the app into the background? Thanks |
We have the same issue with our app. When you go to background and back, there is a high chance of exactly this crash: EXC_BAD_ACCESS at fira.worker thread. There is nothing much you can conclude from the crash. We don't use Unity, it's native iOS app. We use crashlytics, analytics, and notifications. When going to the background (and back) we don't log analytics event or non-fatals to crashlytics, so I really don't know what's causing this. |
@itsJoKr As there is a high change of crashing, could you please enable debug mode, reproduce the crash and share the console logs with us? It will pin point what logic is causing the issue. |
@itsJoKr : do you have any sample project that we can reproduce? Thanks |
@baolocdo Thanks! |
Closing for now since this has become inactive. @itsJoKr if you have a stack trace or reproducible example, please share it and I'll reopen the issue. |
Uh oh!
There was an error while loading. Please reload this page.
Environment
Describe the problem
What happened?
When user quits our apps, crash is occured.
That problem can be checked on crashlytics.
log
Podfile.lock
PODS:
DEPENDENCIES:
SPEC CHECKSUMS:
AdColony: e657145620acd54033e38cc18902eed01d3c456d
AppLovinSDK: 485b91ee21c189bb2dffc3234c9e79d65d816a10
Crashlytics: 79e236942ca1e7fc641df1feb9a275360a78ab6a
Fabric: 5911403591946b8228ab1c51d98f1d7137e863c6
FBAudienceNetwork: 20a0e3d20e377dbb6708365e4c6d0711bf08ca97
Firebase: 9548cae14d69718add12d75a5b312893f7ef89c7
FirebaseAnalytics: 76f754d37ca5b04f36856729b6af3ca0152d1069
FirebaseAuth: 22f8a5170f31d1f111141950590f071f35df3229
FirebaseCore: 9a6cc1e3eaf75905390f9220596ad4fd8f92faee
FirebaseCrash: cded0fc566c03651aea606a101bc156085f333ca
FirebaseInstanceID: 24958382a1011bba5aaff37e334e7a650b9118f5
FirebaseMessaging: eaf1bfff0193170c04ea3ba3bfe983f68f893118
FirebaseStorage: 0cca42d9b889a0227c3a50121f45a4469fc9eb27
Flurry-iOS-SDK: 2fe79828380c013d442ac2233f55568f82354de7
Google-Mobile-Ads-SDK: 113804f266381a30f982ad3c18063d4e0155414f
GoogleMobileAdsMediationAdColony: e661e4c83a3fd95675b7b57b34d5947dd245b611
GoogleMobileAdsMediationAppLovin: 80dd55f6d6905ed09a807b69c9970aa4c6fc7062
GoogleMobileAdsMediationFacebook: c87fa3a31b3df941662b5380750b76bb1f216540
GoogleMobileAdsMediationUnity: 23b047cfbf2fdbb4bea7f4ee5de787af7071dce4
GoogleMobileAdsMediationUnityAdsSDK: f3fc4bf2f8718ed07aac7042f008a4b9cc88a962
GoogleMobileAdsMediationVungle: e3d990245f804d22f061fcc7105009a88a77df64
GoogleToolboxForMac: 2501e2ad72a52eb3dfe7bd9aee7dad11b858bd20
GTMSessionFetcher: ebaa1f79a5366922c1735f1566901f50beba23b7
KochavaTrackeriOS: b3ac3ed18755f67b71a9a93a7f8f03a408305d5b
nanopb: 5601e6bca2dbf1ed831b519092ec110f66982ca3
Protobuf: 8a9838fba8dae3389230e1b7f8c104aa32389c03
VungleSDK-iOS: af3aa92d0f4a923505a9416646ffef5250592150
PODFILE CHECKSUM: 7e92a8f3551061ea839c1b57a47f300a9f800eae
COCOAPODS: 1.2.1
The text was updated successfully, but these errors were encountered: