[Huge ANRs Spike]

[Muhammad Waqas]

Huge anr spike after update admob unity sdk from 8.2.0 to 8.7.

I post issue on admib unity github they directed me to this group for support.

Please check admob unity github link to check anrs details.

https://github.com/googleads/googleads-mobile-unity/issues/3227

[Mobile Ads SDK Forum Advisor]

Hi,

You can enable optimized SDK initialization and ad loading to improve the overall responsiveness of ads and help prevent "Application Not Responding" (ANR) errors on your app. This guide outlines the changes you need to make to enable these optimizations. Kindly refer to Optimize initialization and ad loading for more information.
 

This message is in relation to case "ref:!00D1U01174p.!5004Q02s05Cu:ref" (ADR-00227939)

Thanks,
 

Mobile Ads SDK Team

[Muhammad Waqas]

I already enabled these two options.

[Muhammad Waqas]

ANR details

[Mobile Ads SDK Forum Advisor]

Hi,

I will check with our team regarding your query and one of my team members will reach out to you once we have an update on this. Meanwhile, your patience is highly appreciated. 

[Muhammad Waqas]

[Muhammad Waqas]

Crash reaches upto 9% and google play console issue me a warning about bad behavior. Now who can tell play console team its because of admob. I think i have to shift away from admob.

[Muhammad Waqas]

ANRs*

[Mobile Ads SDK Forum Advisor]

Hello Muhammad,

Thanks for reaching out.

We are currently investigating with the engineering team and will get back to you as soon as there is an update.


Regards,
Joshua

ref:!00D1U01174p.!5004Q02s05Cu:ref

[Muhammad Waqas]

Still no solution provided by google team.

[ANGELO KELLEY]

Hi all,

We also met the same issue as Muhammad. ANR peaks suddenly from 10th April. It peaks with all the released versions which used to work very well with ANR. 

The rate used to be around 0.4%.  And after the below ANR occurrence rose, it is 0.8% which means bad behavior. 

The anr is com.google.android.gms.policy_ads_fdr_dynamite@240304709 @ 240304704034.602821767.602821767 - m.ajm.bc. And the stacktrace is just the same as Muhammad provied. 

Please look into it very seriously because it broke the online version which is released several weeks ago. 

Thanks 

Treaven

[Neon Gaming]

What i can confirm is that it is caused by MobileAds.Initialize(initStatus => { }); . I found it through Crashlytics custom keys.

Crashlytics.SetCustomKey("AdsManager", "Enter_InitializeAds");
MobileAds.SetRequestConfiguration(requestConfiguration);
MobileAds.Initialize((InitializationStatus initStatus) =>
{
    Crashlytics.SetCustomKey("AdsManager", "MobileAds.Initialize_Action");
});

And mentioned ANR, keys log on firebase crashlytics always ends on  Crashlytics.SetCustomKey("AdsManager", "Enter_InitializeAds");
Means this is the last key logged before anr happened at  MobileAds.Initialize.

[Neon Gaming]

For me GMA 23.0.0 ,  22.6.0 ,  22.5.0 is has this anr. Before that i was using GMA 22.0.0 (GMA Unity 8.2.0) and has no anr