Admob init ANR，please fix it

[ssjc...@gmail.com]

"main" prio=5 tid=1 Suspended
| group="main" sCount=2 dsCount=0 flags=1 obj=0x71e9cbb8 self=0xb4000072f4e10800
| sysTid=27848 nice=-10 cgrp=default sched=0/0 handle=0x737c6f8500
| state=S schedstat=( 11582655965 257494167 111153 ) utm=368 stm=790 core=1 HZ=100
| stack=0x7fd7625000-0x7fd7627000 stackSize=8192KB
| held mutexes=
at com.google.android.gms.ads.internal.js.ai.b(:com.google.android.gms.policy_ads_fdr_dynamite@212104400@212104400057.375149532.375149532:3)
at com.google.android.gms.ads.internal.js.ai.a(:com.google.android.gms.policy_ads_fdr_dynamite@212104400@212104400057.375149532.375149532:5)
- locked <0x0436e729> (a java.lang.Object)
at com.google.android.gms.ads.internal.js.function.n.b(:com.google.android.gms.policy_ads_fdr_dynamite@212104400@212104400057.375149532.375149532:0)
at com.google.android.gms.ads.internal.e.b(:com.google.android.gms.policy_ads_fdr_dynamite@212104400@212104400057.375149532.375149532:19)
at com.google.android.gms.ads.internal.e.a(:com.google.android.gms.policy_ads_fdr_dynamite@212104400@212104400057.375149532.375149532:0)
at com.google.android.gms.ads.nonagon.au.h(:com.google.android.gms.policy_ads_fdr_dynamite@212104400@212104400057.375149532.375149532:8)
at com.google.android.gms.ads.internal.client.br.bS(:com.google.android.gms.policy_ads_fdr_dynamite@212104400@212104400057.375149532.375149532:23)
at fz.onTransact(:com.google.android.gms.policy_ads_fdr_dynamite@212104400@212104400057.375149532.375149532:4)
at android.os.Binder.transact(Binder.java:1050)
at com.google.android.gms.internal.ads.zzgw.zzb(com.google.android.gms:play-services-ads-base@@19.7.0:21)
at com.google.android.gms.internal.ads.zzyi.zza(com.google.android.gms:play-services-ads-lite@@19.7.0:26)
at com.google.android.gms.internal.ads.zzzn.zza(com.google.android.gms:play-services-ads-lite@@19.7.0:36)
- locked <0x0f61904f> (a java.lang.Object)
at com.google.android.gms.ads.MobileAds.initialize(com.google.android.gms:play-services-ads-lite@@19.7.0:6)
at com.google.android.gms.ads.MobileAds.initialize(com.google.android.gms:play-services-ads-lite@@19.7.0:8)
at com.da.config.AdManagerHelper.initAd(AdManagerHelper.java:272)
at com.da.config.AdManagerHelper.<init>(AdManagerHelper.java:140)
at com.da.config.AdManagerHelper.getInstance(AdManagerHelper.java:174)
at com.xmode.launcher.Launcher$120.run(Launcher.java:15546)
at android.os.Handler.handleCallback(Handler.java:938)
at android.os.Handler.dispatchMessage(Handler.java:99)
at android.os.Looper.loop(Looper.java:255)
at android.app.ActivityThread.main(ActivityThread.java:8194)
at java.lang.reflect.Method.invoke(Native method)
at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:632)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1049)

[Mobile Ads SDK Forum Advisor]

Hello Ssjcfiaw,

Thank you for reaching out to us.

For us to further investigate this, could you please provide the following details via Reply privately to author option or send it directly to mobileads...@gmail.com? Kindly inform us on this thread if you sent it directly to the email provided.

• Sample app where ANR happening
• Device name and versions affected
• SDK version
•  Percentage occurrence of the ANRs

Regards,

Princess Pamela Pineda Mobile Ads SDK Team

 

 

ref:_00D1U1174p._5004Q2NUzhO:ref

[Roman]

Hey Admob Team,

There was already multiple threads with exact the same issue caused by "policy_ads_fdr_dynamite". You've been provided with tons of stacktraces and logs.

Please finally do something about this issue

[Mobile Ads SDK Forum Advisor]

Hi Roman,

Thank you for getting back to us.

As per checking, this has been flagged by other publishers as well and is still under investigation. We'll let you know the soonest the team provide their feedback.

Regards,

Teejay Wennie Pimentel Mobile Ads SDK Team

ref:_00D1U1174p._5004Q2NUzhO:ref

[Roman]

It seems like situation worsened with the latest Admob sdk update for Unity, we already excluded more than 30% of traffic (Android 5 -8) from showing Admob Ads, but now new version generate lots of ANRs.

Guys, please wake up,  you've been tossing this issue for months!

ANRbrightness_1Huawei Y9 Prime 2019brightness_1Android 10 (SDK 29)

  at java.lang.Object.wait (Native method)

  at java.lang.Object.wait (Object.java:442)

  at java.lang.Object.wait (Object.java:568)

  at com.google.android.gms.ads.exoplayer3.n.d (com.google.android.gms.policy_ads_fdr_dynamite@212910700@212910700057.385466565.385466565:2)

  at com.google.android.gms.ads.internal.video.exoplayer3.ab.at (com.google.android.gms.policy_ads_fdr_dynamite@212910700@212910700057.385466565.385466565:3)

  at com.google.android.gms.ads.internal.video.gmsg.exoplayer3.d.e (com.google.android.gms.policy_ads_fdr_dynamite@212910700@212910700057.385466565.385466565)

  at com.google.android.gms.ads.internal.webview.ac.aS (com.google.android.gms.policy_ads_fdr_dynamite@212910700@212910700057.385466565.385466565)

  at com.google.android.gms.ads.internal.webview.ac.destroy (com.google.android.gms.policy_ads_fdr_dynamite@212910700@212910700057.385466565.385466565:7)

  at com.google.android.gms.ads.internal.webview.y.destroy (com.google.android.gms.policy_ads_fdr_dynamite@212910700@212910700057.385466565.385466565:5)

  at com.google.android.gms.ads.internal.webview.q.f (com.google.android.gms.policy_ads_fdr_dynamite@212910700@212910700057.385466565.385466565:2)

  at com.google.android.gms.ads.internal.gmsg.y.a (com.google.android.gms.policy_ads_fdr_dynamite@212910700@212910700057.385466565.385466565:4)

  at com.google.android.gms.ads.internal.webview.q.i (com.google.android.gms.policy_ads_fdr_dynamite@212910700@212910700057.385466565.385466565:3)

  at com.google.android.gms.ads.internal.webview.q.e (com.google.android.gms.policy_ads_fdr_dynamite@212910700@212910700057.385466565.385466565:9)

  at com.google.android.gms.ads.internal.webview.ai.run (com.google.android.gms.policy_ads_fdr_dynamite@212910700@212910700057.385466565.385466565:4)

  at android.os.Handler.handleCallback (Handler.java:888)

  at android.os.Handler.dispatchMessage (Handler.java:100)

  at atb.a (com.google.android.gms.policy_ads_fdr_dynamite@212910700@212910700057.385466565.385466565)

  at com.google.android.gms.ads.internal.util.f.a (com.google.android.gms.policy_ads_fdr_dynamite@212910700@212910700057.385466565.385466565:1)

  at atb.dispatchMessage (com.google.android.gms.policy_ads_fdr_dynamite@212910700@212910700057.385466565.385466565)

  at android.os.Looper.loop (Looper.java:213)

  at android.app.ActivityThread.main (ActivityThread.java:8178)

  at java.lang.reflect.Method.invoke (Native method)

  at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run (RuntimeInit.java:513)

  at com.android.internal.os.ZygoteInit.main (ZygoteInit.java:1101) 

[Mobile Ads SDK Forum Advisor]

Hi Roman,

I've added your findings regarding on updating your SDK to the latest version. I'll let you know the soonest they team provide their feedback.

[Bog]

We're having exactly the same issue

пятница, 24 сентября 2021 г. в 12:42:50 UTC+3, mobileadssdk:

[Mobile Ads SDK Forum Advisor]

Hi Bog,

Thank you for raising this to us.

The team is currently conducting an investigation on this. We'll let you know the soonest we have our findings.

[Mobile Ads SDK Forum Advisor]

Hi All,

I hope you're doing well.

I just want to circle back on this. The team mentioned that this has been fixed. Feel free to come back to us if you still encounter any issues regarding this.

Regards,

Princess Pamela Pineda Mobile Ads SDK Team

ref:_00D1U1174p._5004Q2NUzhO:ref

[Roman]

Hello,

Good news, thank you. Although I don't see the Google Ads Unity SDK being updated.

Do we need to update SDK in order to get the fix?

[Mobile Ads SDK Forum Advisor]

Hi Roman,

Thank you for your response.

I would suggest using the latest SDK and checking if it is now working on your end. Kindly let us know if you encounter any issues.

[Roman]

Hello

The latest Mobile Unity SDK was released more than 3 months ago, do we need to wait for a new update to be released? Or everything should be fine with that one.
If so, then the cause of this issue must be some server-side problem, and it fixed on your side, correct?

Thank you

[Mobile Ads SDK Forum Advisor]

Hi Roman,

Thank you for your response.

Can you confirm if your error that was encountered has com.google.android.gms.ads.internal.omid? If yes, this is the one that the team mentioned that was already fixed. If you encounter any other errors, kindly provide us with any logs that you may encounter. We also suggest using the latest version of unity that is available.

[tonyev...@gmail.com]

When the new version will be fixed, please let me know

[Mobile Ads SDK Forum Advisor]

Hi there,

Thank you for joining in. There are different concerns expressed in this thread, the issue reported September 17, 2021 is solved.  The issue reported September 24, 2021 is expected to be fixed at the end of April, if it isn't, please get back to us. The issue reported April 3, 2022 can be tracked in its Github issue.

Regards,

Aryeh Mobile Ads SDK Team

ref:_00D1U1174p._5004Q2NUzhO:ref

[Mobile Ads SDK Forum Advisor]

Hi All,

I hope you're doing well.

I just want to circle back on this. The team mentioned that this has been fixed. Feel free to come back to us if you still encounter any issues regarding this.

Regards,

Princess Pamela Mobile Ads SDK Team

ref:_00D1U1174p._5004Q2NUzhO:ref

[Roman]

Hello

What does this mean? There was no update of Google Mobile Ads SDK? How it can be fixed?

Thanks

[Mobile Ads SDK Forum Advisor]

Hi Roman,

Thank you for your response.

Can you confirm if your concern is related to the com.google.android.gms.ads.internal.omid? If yes, this is the one that the team mentioned that was already fixed. If you still encounter any other errors, kindly provide us with any logs that you may encounter. We also suggest using the latest version of unity that is available.