-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
Frequent NSInternalInconsistencyException Crashes After Displaying Full-Screen Ads #3722
Comments
We have the exact same issue! We could identify that it seems to be related to Vungle (Liftoff) Interstitial ads, as when we disabled them, the crashes went down. Not sure if also rewarded ads are problematic, but atleast interstitials of them are defintively breaking. Also Vungle seems sometimes on iOS to play sound even so the phone is muted :) Just checked: |
Thanks for the report, I will let the IOS team know about this. So to confirm, the replication steps seem to be:
Corect? |
Thanks for following up! I’d like to clarify my own situation.
If there’s a known workaround or any suggestions you can provide, I’d really appreciate it. Thank you for looking into this and for passing the info along to the iOS team! |
No :) To replicate the issue you need Admob 9.5.0 + Liftoff mediation adapter. Disabling liftoff ads (on the admob platform) for interstitials helped us to REDUCE the errors (basically confirming for us, that liftoff ads are the problem). So if you want to see crashes, you need to have liftoff ads of course enabled. |
Thanks for the update, I will let the team know. |
[REQUIRED] Step 1: Describe your environment
[REQUIRED] Step 2: Describe the problem
Steps to reproduce:
We do not have a reliable step-by-step reproduction procedure. However, Crashlytics frequently reports the following crash after users have viewed a full-screen ad. It appears to occur around the time the ad is dismissed.
The crash does not happen for every ad impression, and we haven’t been able to reproduce it reliably in our own testing. We do not call Application.Quit() or exit(0) anywhere in our code.
Below is a snippet of the crash log:
If there is any known issue or recommended workaround regarding this crash, we would appreciate any guidance. Thank you!
The text was updated successfully, but these errors were encountered: