-
Notifications
You must be signed in to change notification settings - Fork 428
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
Firebase messaging caused iOS Unity app crash on startup (4.0.2, not always, rendering) #104
Comments
Hi @sigono-chao3 we don't invoke Unity's rendering API directly, we do however swizzle the didFinishLaunchingWithOptions app delegate method present to setup messaging, dynamic links and invites in the call stack you've shared. Any chance you have additional information to help us reproduce? The assert does look very dodgy. Aug 22 11:52:33 Sigono-de-iPhone heaven01[679] : Uncaught exception: NSInternalInconsistencyException: [UnityAppController renderingAPI] called before [UnityAppController selectRenderingApi] Suggests that the call order is the problem here in Unity's framework. Are you sure this isn't a known issue for Unity 5.6.3f1 on iOS? |
@sigono-chao3 any luck finding the root cause of your issue? |
@stewartmiles |
Hello, we installed Firebase 4.0.2 to our Unity game. And it works quite well. However, when we try to send our game for Apple review, the reviewer said our game crashed on startup. The call stack shows the app crashed somewhere in Unity Metal code, and we ended up forcing our game running on OpenGL ES3. Today we got it reproduced in house and it seems related to how Firebase invokes Unity rendering API and I would like to report it:
Unity version: 5.6.3f1 (macOS 10.12.5)
Device: iPhone5 A1429
Device log:
Symbolicated main thread call stack
Thank you very much for your help
The text was updated successfully, but these errors were encountered: