-
Notifications
You must be signed in to change notification settings - Fork 433
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 when Application.Quit #367
Comments
Hi I'm also having this on both Android and iOS. For me itt seems that the error "object xxxxxxx should be deleted before the app xxxxxxx it depends upon" which is shown for auth, database and functions has been set to an exception for Functions. You can see below that there are three of these debug logs - one for database, auth and functions. Only the functions is throwing an exception. From your log it seems like crashlytics might be doing the same thing possibly.
|
This is similar to the first issue reported in #368 As described in #368, I think this is due to FirebaseApp got finalized before FirebaseCrashlytics and it asserted at C++ level. This actually should be allowed. We can change that pretty fast. At the meantime, please just try to catch the exception thrown from Application.Quit(). I am a bit skeptical if this helps. Another option is to downgrade the Firebase SDK to any one prior to 5.6.0, which is the version introducing the issue. You should be able to download the older SDK using the link like the following (replace the version number if needed) Sorry for the inconvenience and we are working on the fix for this. |
Thank you very much for the help. Try / catching the exception indeed doesn't help. |
We are seeing the same issue in our app: 05-21 16:38:07.091 22932 22974 I Unity : Crashlytics object 0x83ff0160 should be deleted before the App 0x8d84c920 it depends upon. We added in the "OnApplicationQuit" callback the following lines:
We added these lines to fix a SIGSEV crash we encountered when opening the app without internet, then closing the app, then opening it again with internet. Without this Dispose call, it would crash every time in this flow. It appears that in our case, the trigger of the error message ("Crashlytics object xxxxx should be deleted before the App xxxxxxx it depends upon") is the call to Dispose. Will your fix solve this case as well? We are using: |
The fix is ready and will be in the next release. I will update once the release is live. |
I've same error on Android after update from 5.6.1 > 6.0.0, any ETA for the next release? Unity editor version: 2019.1.5f1 |
@AllanRW We're finalizing the next release, and it should hopefully be out today or tomorrow. I'll update this issue once it's live. |
@Ruco @MichaelPageArtrix @giliwerner @AllanRW |
I updated to the latest Firebase unity plugin (6.1.1), but I still see an issue when closing the app with Application.Quit()... I see these lines in the adb logs: And when doing this flow, thee app fails to load (opening the app will only display a black screen):
|
"Crashlytics object 0x8c7ff580 should be deleted before the App 0x84f727c0 it depends upon." is just a warning message and it should not do any harm. Are you seeing any issue, like crash, other than the black screen problem? Regarding to the black screen issue, are you able to reproduce it using Crashlytics quickstart, ex. add Application.Quit() in the sample. Also, could you provide the log when you see the black screen? Thank you |
Please fill in the following fields:
Unity editor version: 2018.1.9f2
Firebase Unity SDK version: 6.0.0
Firebase plugins in use (Auth, Database, etc.): Analytics, Crashlytics, RemoteConfig
Additional SDKs you are using (Facebook, AdMob, etc.): AdMob (+ FAN & InMobi as mediation networks)
Platform you are using the Unity editor on (Mac, Windows, or Linux): Windows
Platform you are targeting (iOS, Android, and/or desktop): Android
Please describe the issue here:
When calling Application.Quit(), often, but not always. A crash occurs.
Relevant parts of logcat:
Any help that can be offered with this will be highly appreciated.
Already spent way too much time on this issue.
Thanks
The text was updated successfully, but these errors were encountered: