iOS crashes on AppLovin's rewarded ads

[emreyanik]

Step 0: Are you in the right place?

• For general technical questions, or help with project-specific issues like setting up ads in
  your app, reach out to our support team on the
  Developer Forum.

• For assistance with your AdMob account, reach out to
  AdMob Support.

• For feedback on our documentation,
  send your feedback by pressing the Send Feedback button at the top right of the
  documentation page you are on.

• For issues related to the code in this repository, continue filing this GitHub issue.

• Once you've read this section and determined that your issue is appropriate for
  this repository, please delete this section.

[REQUIRED] Step 1: Describe your environment

• Unity version: 2021.3.18f1
• Google Mobile Ads Unity plugin version: 8.4.0
• Platform: iOS
• Platform OS version: iOS 14-15-16
• Any specific devices issue occurs on: _____
• Mediation ad networks used, and their versions:

Adapter	Version
Admob	6.8.0
AppLovin	6.8.0
Chartboost	4.2.0
DTExchange	3.1.5
IronSource	2.3.1
Meta	3.10.0
Vungle	3.9.2
Unity	3.7.1

[REQUIRED] Step 2: Describe the problem

We are on production and we can't reproduce on our side but we are getting crash reports from firebase. When we look in to stack trace we found out that crash triggered by AppLovin adapter.

Crash Reason:
Crashed: com.apple.main-thread
EXC_BAD_ACCESS KERN_INVALID_ADDRESS 0x0000000000000050

File:
GoogleMobileAds.iOS.cpp
ReversePInvokeWrapper.RewardedAdClient_RewardedAdUserDidEarnRewardCallback

Stack Trace:
stackTrace.txt

[NVentimiglia]

@emreyanik

Thank you for the error report. I will take a look at this and report back when we have next steps.

b/294275881

[emreyanik]

Hi @NVentimiglia

We have upgraded the Google Mobile Ads Unity plugin to version 8.5.1 where this issue has been fixed. But we are getting the same crash reports from production (updated version). I have attached the stack trace.

stacktrace.txt

[NVentimiglia]

@emreyanik Thank you for the update. feel free to reopen if you get this error on an updated plugin.

[emreyanik]

Hi @NVentimiglia

I think there is a misunderstanding. In My last comment i tried to explain that we are getting the same crash reports from latest plugin (8.5.1). I've also attached stack trace.

[OldSlash]

Hey @emreyanik did you tried to upgrade Unity? We have exact the same issue and from stack it seems it could be also 2021.3.18f1 issue, because of GC flow.

[emreyanik]

Hi @OldSlash, unfortunately updating of Unity is not easy for our product due to QA and production risks. But thanks for the info.

[OldSlash]

Thank you, @emreyanik, for your response. Updating Unity is a challenging task for us as well. Anyway if my company will decide to update Unity and it will help, I'll be sure to provide a response.

[xsheen7]

same issue