-
Notifications
You must be signed in to change notification settings - Fork 35
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
iOS Crash #419
Comments
Hi @7SwordsDev , can you share the full stcktrace for the crash. That would help us debug the issue further |
I use applovin and add mediation to use it normally. However, when I put the product on the appstore, firebase crashlytic reported a crash and this message. Besides that, I don't have any further notes. |
You should be able to get the full stacktrace from firebase. There would be a |
Do you mean this txt is correct?
|
Yes, this is helpful. Could you also share the list of all the adapters included in the project (a screenshot of our Integration Manager). |
Hi, we got the same report from other developers and they noticed this started when they added Moloco. At the moment we have a theory that Moloco introduces something into the build that ends up breaking JSON in some way and leads to the crash. Given the above integration manager screenshot, you integrated Moloco in this affected build as well. Would you mind trying uninstalling Moloco and see if the crashes still persist? In the meantime, we're investigating together with Moloco and I'll let you know if/when we find the underlying issue. |
I will try this. Thanks! |
This issue is stale because it has been open for 30 days with no activity. |
MAX Plugin Version
6.6.1
Unity Version
2022.3.37
Device/Platform Info
iPhone/Ipad
Current Behavior
__98-[ALMediationAdapterWrapper loadNextAdForAdUnitIdentifier:adapterParameters:mediatedAd:andNotify:]_block_invoke
EXC_BAD_ACCESS (KERN_INVALID_ADDRESS)
Expected Behavior
No response
How to Reproduce
log firebase Crashlytics dashboard
Additional Info
No response
The text was updated successfully, but these errors were encountered: