-
Notifications
You must be signed in to change notification settings - Fork 40
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] Il2CppExceptionWrapper crash on iOS #1195
Comments
I couldn't figure out how to label this issue, so I've labeled it for a human to triage. Hang tight. |
Hey @OguzFARSAK, thanks for reaching out. According to the stacktrace, I'm guessing that the issue might be coming from Firestore.
Could you share any code snippets that you're executing with relation to Firestore? It'll help speed up our investigation. Thanks! |
Hey @OguzFARSAK. We need more information to resolve this issue but there hasn't been an update in 5 weekdays. I'm marking the issue as stale and if there are no new updates in the next 5 days I will close it automatically. If you have more information that will help us get to the bottom of this, just add a comment! |
Hello. We are facing the same issue. We don’t have Firestore, only analytics, crashlytics, remote config. |
Here is stacktrace. stacktrace.txt Libraries: Unity version: 2022.3.45 |
Also, we had this issue with Firebase 12.3.0. There was a situation when we manually logged an exception in the game, and Crashlytics crashed at the same time as the exception was logged. Then we removed manual exception logging and updated Firebase to 12.4.1, but this crash hasn't gone away, and this crash is massively affecting our users. Please let me know if there is any possible fix. |
Hey @coffee-lady, thanks for the extra details. I took a look in the stacktrace, but it doesn't show any details that the crash is coming from Firebase products. I noticed that there were multiple threads indicating |
Yes, the reason is the previous situation with manual exception logging (Debug.LogException) and related crash. For example there was 62 manually logged non-fatal exceptions and 62 crashes with this stacktrace. |
That is interesting, could you share some code snippets with the usage of Firebase so we can take a look at what went wrong? If there's any chance you could share an MCVE, that'll help us investigate this faster. Thanks! |
Hello. I've investigated this issue and I found that this crash happened in unusual circumstances. There was null reference exception in our code that was thrown in another thread, not main. Crashlytics couldn't receive correct stacktrace and I was able to get right stacktrace only thanks to another service of crash reporting. Please improve collecting stacktraces in such circumstances like in another services if this is possible. |
Great to hear you were able to get the stacktrace, @coffee-lady. While we really want to help improve our product for better customer experience, without any specific details of what went wrong such as MCVEs, code snippets, or steps to reproduce the behavior, it would be very difficult to determine what went wrong. Nonetheless, thank you for sharing these details! |
Description
Fatal Exception: Il2CppExceptionWrapper on iOS app
We also tried with Firebase sdk v12.4.0
stacktrace.txt
Reproducing the issue
We can not reproduce
Firebase Unity SDK Version
12.6.0 and 12.4.0
Unity editor version
2022.3.55
Installation Method
.unitypackage
Problematic Firebase Component(s)
No response
Other Firebase Component(s) in use
Analytics, Crashlytics, Firestore, Messaging, Remote Config
Additional SDKs you are using
Applovin Max : 8.0.1
GoogleMobile Ads: 9.5.0
Facebook: 17.0.0
Adjust: v5
GameAnalytics: 7.10.3
Targeted Platform(s)
Apple Platforms
Unity editor platform
Mac
Scripting Runtime
IL2CPP
Release Distribution Type
Pre-built SDK from https://firebase.google.com/download/unity
Relevant Log Output
If using CocoaPods for Apple platforms, the project's Podfile.lock
Expand
Podfile.lock
snippet👀 Replace this line with the contents of your Podfile.lock!
The text was updated successfully, but these errors were encountered: