Reproducable : MobileAds.Initialize() taking 8 seconds.

[stevieh...@gmail.com]

We've seen a recent increase in ANR's caused by input dispatching timing out. It's tipped us over the bad behaviour threshold. More and more bottom end android devices are starting to suffer with this as they become more popular.

The reason for this is MobileAds.Initialize is taking 8 seconds, which blocks the main thread. (version 'com.google.android.gms:play-services-ads:20.4.0') I if spend time tapping the screen during this period I get ANR's and warning regarding timed-out touches.
 

There is nothing we can do with this. There's no optimisations we can do. We even created a pre-cached webview to stop that happening inside MobileAds.Initialize. 

I've attached the profile showing the blocking call on the main thread. 7.95 seconds doesn't give the input despatcher time to service inputs, hence the ANR's.

This needs to be fixed urgently. 

I'll provide any info you need.

I look forward to hearing for you,

Regards,

Steve.

[stevieh...@gmail.com]

The test device is a lenovo a2020a40.

[Roman]

Hello Steve,

Many developers are facing this issue, for now Admob team ignores it.

Check this thread https://groups.google.com/g/google-admob-ads-sdk/c/6LfTaInDGtU

[Mobile Ads SDK Forum Advisor]

Hello Steve,

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
• Steps to replicate
• Full stack trace
• Device and version affected

Regards,

Princess Pamela Pineda Mobile Ads SDK Team

ref:_00D1U1174p._5004Q2QF41N:ref

[Mobile Ads SDK Forum Advisor]

Hello Roman,

Thank you for reaching out to us.

There are different ways/error the ANR are causing. With regard to your previous concern on the other thread, the team are currently working on it. I humbly ask for your patience here in the meantime.

[Roman]

Thank you for reply.

But if you check the Steve' screenshot, you see that the stack trace is exactly the same as reported many times on this forum.

[Mobile Ads SDK Forum Advisor]

Hi Roman,

Thank you for the response. Please know that we have brought this issue to our team and know that it is talked about often. We are working hard to get this resolved. With that being said let me raise this to my team and see if someone can give you an answer than what we can give.

Regards,

William Pescherine Mobile Ads SDK Team

ref:_00D1U1174p._5004Q2QF41N:ref

[stevieh...@gmail.com]

Hi Mobile ads team,

<I've added this here, in case its useful to others, feel free to contact me privately>

Unfortunately I'm extremely busy. There is no way I'll ever be able to provide you with a minimal app. The steps to replicate are to run our app

and tap quickly on the screen when MobileAds.Initialize() is being called.

Fortunately the flame graph tells you everything you need to know (including a callstack). The main thread is blocked by MobileAds.Initialize() There is nothing I could be doing on any other thread

that would be able to affect this. This is purely down to whatever is happening in that routine as it spends 100% of its time in that routine.

My hunch is that the processing being carried out in this routine is too much for these lower spec (but recent) devices (mostly armv7) and the routine needs splitting into smaller chunks to allow input to be serviced
between these chunks. 

I'm already creating a dummy webview with a post delay afterwards (to allow input servicing) so that constructing a webview does not add to time spent in the blocking ad init routines.

This device is a Levono A2020a40

Android v5.1.1

Other devices that get these ANR's include:

AT&T U318AA

Orbic Wonder

HTC One (M8)

AT&T U304AA

Cloud (TruConnect) Storm C3

QMobile X36

Cricket U325AC

TCT (Alcatel) Alcatel JOY TAB

RCA 10 Viking Pro

ZTE Blade L210

Umx(Ultimate Mobile Experience) U693CL

Archos 101 Platinum 3G

Sky Devices ASSIST 55

It's not tied to a specific android version, as the ANR occurs on all android versions.

Regards,

Steve.

[Roman]

Hello William,

Thanks for the response. I'm not sure what "working hard" and "talked often" means in Google language, but when people work hard they get work done. Reality is that this issue which is of utmost severity and criticality is here for more than a year, and there no progress.

I understand that you're limited in what you can do here, but since it's clear now, that your developers are not dedicating enough effort to resolve this problem (which should be fixed in terms of days, max 1-2 weeks), and you should report this issue to your managers or other responsible people.

Google spends so much resources on building relationships with developers, but this situation just kills it and renders your company as ignorant and irresponsible towards the community.

Also please provide status report on this bug that we're waiting, and possible ways of mitigating it on our end. 

[Mobile Ads SDK Forum Advisor]

Hello Roman and Steve,

Thank you for reaching out.

We do apologize for any inconvenience caused. We will do our best to move things forward and get the issue resolved.

In the meantime, it will be great if you can provide a complete stack trace in text.

Please let me know if you have any questions.


Regards,
Joshua

 

ref:_00D1U1174p._5004Q2QF41N:ref

[Roman]

Hello Joshua,

Here it is:

#00  pc 000000000008033c  /apex/com.android.runtime/lib64/bionic/libc.so (syscall+28)

  #00  pc 000000000014c1f4  /apex/com.android.runtime/lib64/libart.so (art::ConditionVariable::WaitHoldingLocks(art::Thread*)+148)

  #00  pc 00000000003ae750  /apex/com.android.runtime/lib64/libart.so (art::JNI::CallStaticObjectMethodV(_JNIEnv*, _jclass*, _jmethodID*, std::__va_list)+464)

  #00  pc 00000000017a809c  /data/app/com.google.android.webview--ju__VbYmt17aYeR98oQfA==/base.apk!libmonochrome.so (???)

  #00  pc 0000000002f17174  /data/app/com.google.android.webview--ju__VbYmt17aYeR98oQfA==/base.apk!libmonochrome.so (???)

  #00  pc 0000000002f170d8  /data/app/com.google.android.webview--ju__VbYmt17aYeR98oQfA==/base.apk!libmonochrome.so (???)

  #00  pc 0000000003a6c454  /data/app/com.google.android.webview--ju__VbYmt17aYeR98oQfA==/base.apk!libmonochrome.so (???)

  #00  pc 000000000418d1d4  /data/app/com.google.android.webview--ju__VbYmt17aYeR98oQfA==/base.apk!libmonochrome.so (???)

  #00  pc 000000000418fc68  /data/app/com.google.android.webview--ju__VbYmt17aYeR98oQfA==/base.apk!libmonochrome.so (???)

  #00  pc 00000000017c29fc  /data/app/com.google.android.webview--ju__VbYmt17aYeR98oQfA==/base.apk!libmonochrome.so (???)

  #00  pc 00000000017a745c  /data/app/com.google.android.webview--ju__VbYmt17aYeR98oQfA==/base.apk!libmonochrome.so (???)

  #00  pc 0000000002df3634  /data/app/com.google.android.webview--ju__VbYmt17aYeR98oQfA==/base.apk!libmonochrome.so (???)

  #00  pc 0000000002df3398  /data/app/com.google.android.webview--ju__VbYmt17aYeR98oQfA==/base.apk!libmonochrome.so (???)

  #00  pc 0000000002df1db0  /data/app/com.google.android.webview--ju__VbYmt17aYeR98oQfA==/base.apk!libmonochrome.so (???)

  #00  pc 0000000002df2974  /data/app/com.google.android.webview--ju__VbYmt17aYeR98oQfA==/base.apk!libmonochrome.so (Java_J_N_M1Y_1XVCN+120)

  at J.N.M1Y_XVCN (Native method)

  at org.chromium.content.browser.BrowserStartupControllerImpl.a (chromium-TrichromeWebViewGoogle.aab-stable-460606133:2)

  at org.chromium.content.browser.BrowserStartupControllerImpl.g (chromium-TrichromeWebViewGoogle.aab-stable-460606133:8)

  at y8.run (chromium-TrichromeWebViewGoogle.aab-stable-460606133:23)

  at org.chromium.base.ThreadUtils.f (chromium-TrichromeWebViewGoogle.aab-stable-460606133:2)

  at wA0.h (chromium-TrichromeWebViewGoogle.aab-stable-460606133:41)

  at wA0.b (chromium-TrichromeWebViewGoogle.aab-stable-460606133:20)

  at wA0.j (chromium-TrichromeWebViewGoogle.aab-stable-460606133:2)

  at com.android.webview.chromium.WebViewChromiumFactoryProvider.g (chromium-TrichromeWebViewGoogle.aab-stable-460606133:2)

  at com.android.webview.chromium.WebViewChromium.init (chromium-TrichromeWebViewGoogle.aab-stable-460606133:14)

  at android.webkit.WebView.<init> (WebView.java:432)

  at android.webkit.WebView.<init> (WebView.java:353)

  at android.webkit.WebView.<init> (WebView.java:336)

  at android.webkit.WebView.<init> (WebView.java:323)

  at android.webkit.WebView.<init> (WebView.java:313)

  at com.google.android.gms.ads.internal.webview.ac.<init> (com.google.android.gms.policy_ads_fdr_dynamite@213806100@213806100057.397311113.397311113:1)

  at com.google.android.gms.ads.internal.webview.s.a (com.google.android.gms.policy_ads_fdr_dynamite@213806100@213806100057.397311113.397311113:4)

  at com.google.android.gms.ads.internal.webview.v.a (com.google.android.gms.policy_ads_fdr_dynamite@213806100@213806100057.397311113.397311113:5)

  at com.google.android.gms.ads.internal.js.l.<init> (com.google.android.gms.policy_ads_fdr_dynamite@213806100@213806100057.397311113.397311113:3)

  at com.google.android.gms.ads.internal.js.r.run (com.google.android.gms.policy_ads_fdr_dynamite@213806100@213806100057.397311113.397311113:2)

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

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

  at ato.a (com.google.android.gms.policy_ads_fdr_dynamite@213806100@213806100057.397311113.397311113)

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

  at ato.dispatchMessage (com.google.android.gms.policy_ads_fdr_dynamite@213806100@213806100057.397311113.397311113)

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

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

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

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

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

[Roman]

Devices is Lenovo Tab M10 (HD)

[Roman]

Here is more:

  #00  pc 0000000000070b98  /system/lib64/libc.so (nanosleep+8)

  #00  pc 000000000045c3f4  /data/app/com.app.id-qPizB6enIRBGLfrXRxLK4A==/lib/arm64/libil2cpp.so (???)

  #00  pc 0000000000468ffc  /data/app/com.app.id-qPizB6enIRBGLfrXRxLK4A==/lib/arm64/libil2cpp.so (???)

  #00  pc 000000000047b2b4  /data/app/com.app.id-qPizB6enIRBGLfrXRxLK4A==/lib/arm64/libil2cpp.so (???)

  #00  pc 000000000043cde0  /data/app/com.app.id-qPizB6enIRBGLfrXRxLK4A==/lib/arm64/libil2cpp.so (???)

  #00  pc 00000000002d42c0  /data/app/com.app.id-qPizB6enIRBGLfrXRxLK4A==/lib/arm64/libunity.so (???)

  #00  pc 000000000017ad04  /data/app/com.app.id-qPizB6enIRBGLfrXRxLK4A==/lib/arm64/libunity.so (???)

  #00  pc 000000000017ac1c  /data/app/com.app.id-qPizB6enIRBGLfrXRxLK4A==/lib/arm64/libunity.so (???)

  #00  pc 0000000000000d90  /data/app/com.app.id-qPizB6enIRBGLfrXRxLK4A==/oat/arm64/base.odex (Java_com_unity3d_player_ReflectionHelper_nativeProxyInvoke__JLjava_lang_String_2_3Ljava_lang_Object_2+208)

  at com.unity3d.player.ReflectionHelper.nativeProxyInvoke (Native method)

  at com.unity3d.player.ReflectionHelper.a (unavailable)

  at com.unity3d.player.ReflectionHelper$1.invoke (unavailable)

  at java.lang.reflect.Proxy.invoke (Proxy.java:1006)

  at com.google.android.gms.ads.initialization.OnInitializationCompleteListener.onInitializationComplete

  at com.google.android.gms.internal.ads.zzbdx.zzb

  at com.google.android.gms.internal.ads.zzbnp.zzbK

  at com.google.android.gms.internal.ads.zzhr.onTransact

  at android.os.Binder.transact (Binder.java:675)

  at zf.bb (com.google.android.gms.policy_ads_fdr_dynamite@213806100@213806100057.397311113.397311113:2)

  at com.google.android.gms.ads.internal.initialization.f.e (com.google.android.gms.policy_ads_fdr_dynamite@213806100@213806100057.397311113.397311113)

  at com.google.android.gms.ads.nonagon.initialization.c.run (com.google.android.gms.policy_ads_fdr_dynamite@213806100@213806100057.397311113.397311113:2)

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

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

  at ato.a (com.google.android.gms.policy_ads_fdr_dynamite@213806100@213806100057.397311113.397311113)

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

  at ato.dispatchMessage (com.google.android.gms.policy_ads_fdr_dynamite@213806100@213806100057.397311113.397311113)

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

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

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

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

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

[ca...@degoo.com]

"We do apologize for any inconvenience caused". This is not an "inconvenience". It's a dramatic revenue drop due to the drop in Google Play ranking it causes. Jobs are at stake. Calling it an "inconvenience" shows that you are either unable or unwilling to grasp the severity of the situation. 

[Dino Go]

I am a typical case. My game used to reach 9-10k downloads 1 day and revenue about 2k usd 1 day. 1 year ago I updated the admob sdk and anr rate increased from 0.3% to 0.6 0.7%. Exceeded the bad behavior threshold on the play console. After that the downloads started to drop to 2-3k a day and severely reduced revenue because tier 1 countries no longer see my game.

[Roman]

Hello Joshua, William

We asked for a status update on this bug: what does your team say, when it will be fixed, how developers can mitigate impact of the bug on their side, did you have a talk with Google Play team to remove impact of YOUR BUGS on apps performance?

[Mobile Ads SDK Forum Advisor]

Hello Roman,

Thank you for the additional stack trace.

This issue was already prioritized and our team has been actively looking into it.

We truly understand the severity of the situation and I will ensure we will be working proactively on the fix.

[Roman]

Hello Joshua,

We're desperate for the fix, amount of new ANRs keep growing despite our best efforts: we already excluded around 30% of traffic from Admob and banned hundreds of devices, but  those ANRs keep coming from new ones.

Maybe there is a way to limit impact of this bug on our side, while you're fixing it?

[Mobile Ads SDK Forum Advisor]

Hello Roman,

I truly understand so I will ensure this will keep moving forward.

In addition to the stack trace that you provided previously, would you please also provide the stack trace from all threads?

Regarding the way to limit the impact of this issue, I will communicate with the team and let you know as soon as there is one.

Thanks!

[Roman]

Hello

Thank you. Please also notice that the first message in this thread provides steps how to reproduce the issue.

Here is the stacktrace.

[Roman]

And here is one more 

[Roman]

Hello

I've found a thread with exactly the same issue that has been started 2!!! years and 6!!! months ago.

And Admob people there also "investigating" and asking for more "stack traces". 

https://groups.google.com/g/google-admob-ads-sdk/c/rCZMplesYEc/m/p6VpFfr2BgAJ

[Bog]

Hello

What is the state of this bug? Did your team come up with the fix? We don’t understand why it takes months to fix!

You’ve been given stack traces, ways to reproduce bug and still there is nothing beyond “we’re investigating”…

In a meantime we’re seing growing number of ANRs and new ones coming with no stack traces:

Input dispatching timed out (Waiting to send non-key event because the touched window has not finished processing certain input events that were delivered to it over 500.0ms ago. Wait queue length: 2. Wait queue head age: 37369.4ms.)

com.google.android.gms.ads.AdActivity

вторник, 2 ноября 2021 г. в 13:39:07 UTC+2, Roman:

[Roman]

Hello Joshua, William

One more week has passed without anything from you. Is there a fix on horizon, or any instructions how to resolve it on our side?

We're thinking of rolling back to 2 years old Admob SDK.

There is no other options, given your speed.

[Roman]

New Admob related ANRs with new stacktraces:

JAY-TECH TPC-G1010 Android 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@213806100@213806100057.397311113.397311113:2)

  at com.google.android.gms.ads.internal.video.exoplayer3.ab.aw (com.google.android.gms.policy_ads_fdr_dynamite@213806100@213806100057.397311113.397311113:3)

  at com.google.android.gms.ads.internal.video.gmsg.exoplayer3.e.f (com.google.android.gms.policy_ads_fdr_dynamite@213806100@213806100057.397311113.397311113)

  at com.google.android.gms.ads.internal.webview.ac.aS (com.google.android.gms.policy_ads_fdr_dynamite@213806100@213806100057.397311113.397311113)

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

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

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

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

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

  at com.google.android.gms.ads.internal.webview.q.e (com.google.android.gms.policy_ads_fdr_dynamite@213806100@213806100057.397311113.397311113:8)

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

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

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

  at ato.a (com.google.android.gms.policy_ads_fdr_dynamite@213806100@213806100057.397311113.397311113)

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

  at ato.dispatchMessage (com.google.android.gms.policy_ads_fdr_dynamite@213806100@213806100057.397311113.397311113)

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

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

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

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

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

Samsung Galaxy A11 Android 11 (SDK 30)

  #00  pc 0000000000060cf4  /apex/com.android.runtime/lib/bionic/libc.so (syscall+28)

  #00  pc 00000000001286f3  /apex/com.android.art/lib/libart.so (art::ConditionVariable::WaitHoldingLocks(art::Thread*)+82)

  #00  pc 00000000004a12b7  /apex/com.android.art/lib/libart.so (art::GoToRunnable(art::Thread*)+338)

  #00  pc 00000000004a113d  /apex/com.android.art/lib/libart.so (art::JniMethodEnd(unsigned int, art::Thread*)+8)

  at android.os.BinderProxy.transactNative (Native method)

  at android.os.BinderProxy.transact (BinderProxy.java:605)

  at android.net.IConnectivityManager$Stub$Proxy.getNetworkInfoForUid (IConnectivityManager.java:3118)

  at android.net.ConnectivityManager.getNetworkInfoForUid (ConnectivityManager.java:1394)

  at android.net.ConnectivityManager.getNetworkInfo (ConnectivityManager.java:1388)

  at JZ.e (chromium-TrichromeWebViewGoogle.aab-stable-463807430)

  at JZ.d (chromium-TrichromeWebViewGoogle.aab-stable-463807430)

  at JZ.a (chromium-TrichromeWebViewGoogle.aab-stable-463807430)

  at QZ.onAvailable (chromium-TrichromeWebViewGoogle.aab-stable-463807430)

  at android.net.ConnectivityManager$NetworkCallback.onAvailable (ConnectivityManager.java:3788)

  at android.net.ConnectivityManager$CallbackHandler.handleMessage (ConnectivityManager.java:4073)

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

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

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

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

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

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

[Roman]

William, Joshua

Where is the fix? Issue is here for more than two years now and you've been fooling around people with stack traces and sample apps request, yet nothing is done.

Bug is here and it causes huge number of ANRs.

[Mobile Ads SDK Forum Advisor]

Hello Roman,

We have done CPU profiling for Unity App and non-Unity App using Unity profiler and Android Studio profiler. It took at most 3 seconds even with the profiling overhead.

Would you please provide the below information:

1. If MobileAds.Initialize() issue happens for Unity App or non-Unity App or Both?
2. What mediation Ad networks are enabled?
3. CPU profile using Android Studio profiler and Unity profiler
   • Instructions about how to do CPU profiling
     • https://developer.android.com/studio/profile/cpu-profiler#configurations
     • https://docs.unity3d.com/2020.3/Documentation/Manual/ProfilerCPU.html
   • MobileAds.initialize() CPU profiling with "Trace Java Methods"
   • MobileAds.initialize() CPU profiling with "Sample Java Methods"
   • onInitializationComplete() CPU profiling
   • Unity MobileAds.initialize() CPU profiling
4. Capture an Android bug report while ANR happens
   • Instructions: https://developer.android.com/studio/debug/bug-report
5. Copy the latest ANR stack trace from /data/anr/
   • The command - adb pull "/data/anr/<filename>" traces.txt
   • replace <filename> with the real file name.

[Roman]

Hello

Thank you for response. We were unable to reproduce this bug, although Steve (who started this thread) managed to do it.

1. We're experiencing the issue in Unity App.

1.1. The most susceptible devices are tablets (here we cross bad behavior threshold): Digma DIGMA Optima Prime 3 3G TS7131MG, Lenovo Tab M10 (HD), JAY-TECH TPC-G1010

1.2. The nature of ANRs seems to be periodical, maybe some connectivity issues with involved servers.

1.3. Maybe you can implement some methods that will prevent Admob taking too much time to initialize, and don't initialize it for buggy devices.

2. No mediation ad networks are used.

3-5. We'll try to reproduce the bug and send you stack traces and profiler reports.

Please also check Steve's profiler screen shot in the first message of this thread.

[stevieh...@gmail.com]

Joshua, please read.

This is not a Unity issue, it's an Admob initialisation issue. We don't use the Unity engine or Unity ads.

This started happening when I added the more recent SDK to allow for bidding.

Please look at the first post in this thread. There is a profile already, it shows where all the time is being taken. 


Stacktraces for this ANR are not available. Here's what is reported:

Input dispatching timed out (Waiting to send non-key event because the touched window has not finished processing certain input events that were delivered to it over 500.0ms ago. Wait queue length: 29. Wait queue head age: 5005.6ms.)

If it's taking 3 seconds on your device (which is a long time to block the main thread!) then surely you can see it going to go over the 5 second mark on a less powerful device (lenovo a2020a40 or 
Motorola Moto G (1st Gen)  ). That would cause the above ANR.

There are an increasingly large number of these types of devices. So you may want to get some to test with.

Admob is mediator, with Facebook and Applovin for added provision - These are initialised later and are not at fault. They show up later in the profile for me.

The profile show you which areas you need to work on. I'm a bit disappointed with the lack of headway being made, I've given you lots of insightful information

and feel like nothing is being done about it. 

Regards,

Steve.

[Roman]

Hello Joshua, William

Firebase also has a similar issue, seems like they've been able to pinpoint it to some "internal library".  We noticed that some devices (Lenovo Tab M10 (HD)) trigger Admob & Firebase ANRs at the same time, so maybe they're connected.

Please check 

https://github.com/firebase/firebase-android-sdk/issues/2387

[Mobile Ads SDK Forum Advisor]

Hello Steve and Roman,

Thank you for the additional information.

The reason we asked for Unity profiler is because a stack trace obtained from an Unity app was provided in one of the previous emails.

In addition to the flame chart in the first post, would you please also provide a "Top Down" chart with methods expanded (see figure 3 in this guide ) so that it will show the time for each method?

Please let me know if you have any questions.

[Roman]

Hello Joshua,

We were unable to reproduce this ANRs. Since don't have an access to above mentioned devices (mostly Lenovo), but I guess your team should have one of them. 

Basically pick one of Lenovo tablets (with 1gb of ram preferably) and you'll catch this ANR by following the steps described by Steve in the first post of this thread. There are some most problematic ones:  Lenovo Tab M7,  Lenovo TAB 2 A7-30HC, Lenovo Tab M10 (HD).

[Roman]

Hello

We caught similar Admob induced ANR probably with Chromium set as default on the device, take a look at it please. Looks like it might caused by some connectivity issues.

  #00  pc 0000000000060cf4  /apex/com.android.runtime/lib/bionic/libc.so (syscall+28)

  #00  pc 00000000001286f3  /apex/com.android.art/lib/libart.so (art::ConditionVariable::WaitHoldingLocks(art::Thread*)+82)

  #00  pc 00000000004a12b7  /apex/com.android.art/lib/libart.so (art::GoToRunnable(art::Thread*)+338)

  #00  pc 00000000004a113d  /apex/com.android.art/lib/libart.so (art::JniMethodEnd(unsigned int, art::Thread*)+8)

  at android.os.BinderProxy.transactNative (Native method)

  at android.os.BinderProxy.transact (BinderProxy.java:605)

  at android.net.IConnectivityManager$Stub$Proxy.getNetworkInfoForUid (IConnectivityManager.java:3118)

  at android.net.ConnectivityManager.getNetworkInfoForUid (ConnectivityManager.java:1394)

  at android.net.ConnectivityManager.getNetworkInfo (ConnectivityManager.java:1388)

  at JZ.e (chromium-TrichromeWebViewGoogle.aab-stable-463807430)

  at JZ.d (chromium-TrichromeWebViewGoogle.aab-stable-463807430)

  at JZ.a (chromium-TrichromeWebViewGoogle.aab-stable-463807430)

  at QZ.onAvailable (chromium-TrichromeWebViewGoogle.aab-stable-463807430)

  at android.net.ConnectivityManager$NetworkCallback.onAvailable (ConnectivityManager.java:3788)

  at android.net.ConnectivityManager$CallbackHandler.handleMessage (ConnectivityManager.java:4073)

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

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

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

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

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

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

[Mobile Ads SDK Forum Advisor]

Hello Roman,


Thanks for the additional stack trace.

Can you please the complete stack trace (with the other threads included) and CPU profiling "Top Down" chart (see figure 3 in this guide) as well?

[Roman]

Hey Joshua,

It's ANR we see in Google Play, so no profiler information. Complete stack trace is attached

[Roman]

Hello 

Is there any news on this issue? It's been quite a while.

[Roman]

Hello

A new Admob induced ANRs with Chromium in the stack trace.

[Roman]

And one more related to loading Rewarded video

[ca...@degoo.com]

Any updates on this issue?

1. When will you fix the root cause?

2. When will Google stop punishing publishers for bugs caused by Google?

Best,

Carl

[Roman]

Hello

Today we're seeing a huge burst of Admob-related ANRs, the worst in months...

Are you doing anything to stop this? Or you still waiting someone to debug it and send you a profiler info??

[Mobile Ads SDK Forum Advisor]

Hello Roman,

Thank you for the additional stack trace, we are looking into them.

It seems like those ANRs are not related to `MobileAds.Initialize()` which was originally reported in this thread.

May I ask would you know which type of ANR (e.g. when rewarded ad is loaded) happen the most? 

[Roman]

Hello

There is more `MobileAds.Initialize()` ANRs than those related to rewarded ads, but it seems like they have the same root cause: both are happening in WebView/Chrome while ads are loaded.

Both are also highly sporadic: occurring in bursts and sending your ANR ratio above acceptable minimum.

Thanks 

[Roman]

Joshua, William

It's been quite a while since this problem was spotted, and so far there is no progress on your side.  Why don't you push Google Play team to implement fix to omit developers from your bugs?

We contacted them, but they disregarded this issue.

It's clear there is a few bugs on your side that terrorize many developers out there. There is massive Firebase ANR bug which is ignored by their team for more than a year, which further compounds all your ANRs.

Developers have nothing to do with them, why should we pay for it if you're unable to fix those bugs?

[Bog]

Hello

Is there any update on this issue?

среда, 24 ноября 2021 г. в 10:49:07 UTC+2, Roman:

[Roman]

Hi there

What is the state of this issue? Any progress towards finally getting rid of this?

[Roman]

Joshua, William

What is the state of this bug? 

This bugs seems hopeless, we have a doubts that you're doing something. More and more people switching to other networks because of this.

If Admob SDK will continue to generate such amount of ANRs, there is no other option than to switch to other ads providers.

https://github.com/googleads/googleads-mobile-unity/issues/1825#issuecomment-983697878

[Roman]

Hey Joshua, William

What is the state of this issue? 

[Mobile Ads SDK Forum Advisor]

Hello Roman,

Sorry for the delay.

Our team is going to work with the Unity team on this issue: https://github.com/googleads/googleads-mobile-unity/issues/1825.

Regarding the stack traces you provided previously:

• att-u705aa.txt: It is related to Rewarded LoadAd instead of  `MobileAds.Initialize()` in this thread. Our team is currently looking at it.
• redmi-note-9.txt: It is related to WebView and we have escalated to the corresponding team to look at it.
• samsung-a11-anr.txt: It is not related to Ads.

@Steve: Since you are the original reporter of the issue "MobileAds.Initialize() taking 8 seconds", in addition to the flame chart in the first post, would you mind also providing a "Top Down" chart with methods expanded (see figure 3 in this guide) so that it will show the time for each method?

Thanks!

[Roman]

Hey Joshua,

Why don't you consider cooperating with Google Play to remove Google-related ANRs from vitals. Right now ~95-97% ANRs we see in our apps are produced by Google libraries (mostly Admob & Firebase).

This is just crazy. There are hundreds post on Github, this forum, Reddit and elsewhere on the internet with enraged developers. Still you're ignoring this issue like it is okay.

If it's so widespread and systematic, why not implement the only solution which will free developers from your bugs?

[Roman]

Hello Joshua, William

You have been ignoring the questions about implementing mechanism in Google Play to exclude Google-caused ANRs from developers Android Vitals metrics for a couple months.

Is that something that can be done? It would really resolve much of the problems.

Please let me remind you, that you've been "investigating" this issue with no real progress for about 3 months already, and issue exist for about 2 years.

[Roman]

Hello Joshua, William

The question remains unanswered 

[Roman]

Hello Joshua, William

What is the state of this issue? The question about implementing a fix on Google Play side remains unanswered.

[Roman]

Hello Joshua, William

What is the state of this issue? The question about implementing a fix on Google Play side remains unanswered.

On Tuesday, December 7, 2021 at 4:38:50 AM UTC+2 mobileadssdk wrote:

[ca...@degoo.com]

While debugging I found one potential culprit for the ANR: you are calling a ContentResolver on the main thread when the ads SDK is being initialized.

2021-12-22 17:32:39.880 10850-10850/com.instabridge.android.dev D/StrictMode: StrictMode policy violation; ~duration=1578 ms: android.os.strictmode.CustomViolation: gcore.dynamite
        at android.os.StrictMode$AndroidBlockGuardPolicy.onCustomSlowCall(StrictMode.java:1563)
        at android.os.StrictMode.noteSlowCall(StrictMode.java:2555)
        at sot.a(:com.google.android.gms@201817022@20.18.17 (040700-311416286):0)
        at com.google.android.gms.chimera.container.GmsModuleProvider.query(:com.google.android.gms@201817022@20.18.17 (040700-311416286):3)
        at android.content.ContentProvider.query(ContentProvider.java:1379)
        at android.content.ContentProvider.query(ContentProvider.java:1475)
        at android.content.ContentProvider$Transport.query(ContentProvider.java:278)
        at android.content.ContentProviderNative.onTransact(ContentProviderNative.java:106)
        at android.os.Binder.execTransactInternal(Binder.java:1154)
        at android.os.Binder.execTransact(Binder.java:1123)
    # via Binder call with stack:
        at android.os.StrictMode.readAndHandleBinderCallViolations(StrictMode.java:2358)
        at android.os.Parcel.readExceptionCode(Parcel.java:2318)
        at android.database.DatabaseUtils.readExceptionFromParcel(DatabaseUtils.java:139)
        at android.content.ContentProviderProxy.query(ContentProviderNative.java:472)
        at android.content.ContentResolver.query(ContentResolver.java:1183)
        at android.content.ContentResolver.query(ContentResolver.java:1115)
        at android.content.ContentResolver.query(ContentResolver.java:1071)
        at com.google.android.gms.dynamite.DynamiteModule.zzb(com.google.android.gms:play-services-basement@@17.6.0:10)
        at com.google.android.gms.dynamite.DynamiteModule.zza(com.google.android.gms:play-services-basement@@17.6.0:43)
        at com.google.android.gms.dynamite.DynamiteModule.getRemoteVersion(com.google.android.gms:play-services-basement@@17.6.0:1)
        at com.google.android.gms.internal.ads.zzbei.zzd(com.google.android.gms:play-services-ads-lite@@20.4.0:5)
        at com.google.android.gms.internal.ads.zzbhj.zzw(com.google.android.gms:play-services-ads-lite@@20.4.0:3)
        at com.google.android.gms.internal.ads.zzbhj.zzb(com.google.android.gms:play-services-ads-lite@@20.4.0:8)
        at com.google.android.gms.ads.MobileAds.initialize(com.google.android.gms:play-services-ads-lite@@20.4.0:3)

[Roman]

Hello Joshua, William

What is the state of this issue? The question about implementing a fix on Google Play side remains unanswered.

[Roman]

Hello Joshua, William

What is the state of this issue? The question about implementing a fix on Google Play side remains unanswered.

[Roman]

What is the state of this issue?

[mastef ‎]

Hi, definitely a serious issue for us as well - I've posted more information on our overall ANR degradation :

https://github.com/googleads/googleads-mobile-unity/issues/1825#issuecomment-1002892463

We've been also told by the Google Play team that our ANR rate is too high. I've included the stats from our console showcasing the recent behavior. Also posted more device-related stats

It would be really cool if you guys could figure this issue out.

Thanks!

[Mobile Ads SDK Forum Advisor]

Hello all,

Thank you all for reaching out.

The fix for the ANR is expected to be released in February.

Please let me know if you have any questions.

[Dino Go]

Nice! Thanks! Hope it working well :D

[AntonZhang]

I just wanna know if ANRs are caused by "main-thread ContentProvider query" or some reasons else , what can we do to reduce  Anr rate as far as possible for now

[Mobile Ads SDK Forum Advisor]

Hello Anton,

Thanks for the question.

Would you mind providing a complete stack trace for the ANR that you saw?

[AntonZhang]

Yes , here it is ,thanks for your responding

[servic...@outlook.de]

I too am constantly struggling with ANR's when initializing Admob. Would be really great if this would finally be fixed. See attachment.

[Mobile Ads SDK Forum Advisor]

Hello Duran,

Thank you for the additional information. 

Since you encountered ANR when initializing AdMob, would you please provide the below information as well?

1. CPU profile using Android Studio profiler
   • Instructions about how to do CPU profiling
     • https://developer.android.com/studio/profile/cpu-profiler#configurations
   • MobileAds.initialize() CPU profiling with "Trace Java Methods"
   • MobileAds.initialize() CPU profiling with "Sample Java Methods"
   • onInitializationComplete() CPU profiling
   • Unity MobileAds.initialize() CPU profiling
2. Capture an Android bug report while ANR happens
   • Instructions: https://developer.android.com/studio/debug/bug-report
3. Copy the latest ANR stack trace from /data/anr/
   • The command - adb pull "/data/anr/<filename>" traces.txt
   • replace <filename> with the real file name.

Thank you!

[Juan Manuel Pereyra]

Hi Joshua,

We're planning for a release in March, is there any news on this? 
If there is no solution or this gets delayed, we have to move to another mediation system because your own alg will impose penalties on us for this.

Any news would be welcome at least to take an informed decision.

Regards,

Juan Manuel

[Dino Go]

I have updated new version 20.6.0 but this anr still not fix :(

[Mobile Ads SDK Forum Advisor]

Hello Dino,

Thanks for reaching out.

The fix is not in version 20.6.0 yet, but is expected to be in the future release (in March or April). We will update this thread once there is an update.

Can you attach the stack trace that shows what ANR are you experiencing?

[Dino Go]

Hi! My stacktrace same some people post at here. But i see highest anr is have empty stacktrace.

But I dont know why when i update to version 20.6.0, my anr rate increase from 0.5% to 0.9%.

I see some info about version 21, hope it release soon and fixed this problem. I get tired with this in 2 years. My game get decrease download for 4-5 times...

Thanks!

[Giru bhai]

Dear  Joshua, any update on this ? Why are you misguide developers i..e. you first told it will be resolved in February and then told march or April. Seriously ?

[ca...@degoo.com]

Any updates? 

[Dino Go]

near April. Expect they dont tell the fixed version release at May or June...

[Dino Go]

I try used another mediation and not use admob in one of my games. And this is result about anr rate

[Dino Go]

this is image when used admob

[Roman]

Hello dear Admob team,

What is the state of the issue? 

For the past 8 months we went from your denial of the issue to many broken promises to fix it, first it was "February", now "March-April".

Is the fix on the horizon?

[Mobile Ads SDK Forum Advisor]

Hello Roman,

The ANR fix will be in the coming release, the current ETA is within April.

Thanks!

[mianha...@gmail.com]

its 2nd May , where is the updated SDK ?

[Mobile Ads SDK Forum Advisor]

Hello there,

Thanks for checking in.

The next Android release with the ANR fix is expected to come in ~2 weeks.

Please keep an eye on the release page with the next release.

[ca...@degoo.com]

You first said that the release would come out in February and now you will most likely not make it to May.

https://abc.xyz/investor/other/google-code-of-conduct/ 

"Our reputation as a company that our users can trust is our most valuable asset, and it is up to all of us to make sure that we continually earn that trust. All of our communications and other interactions with our users should increase their trust in us."

Would you say that Google's interactions in this thread have followed your code of conduct by increasing our trust in you or would you say that there's some room for improvement when it comes to your credibility? 

[Roman]

What's even more disgraceful that Admob team initially ignored this issue at least since September when people started reporting it en masse, and it seems like they're started working on it only recently.

You can also find the same ANR reports on this forum that are dating back ~ 2 years ago.

[mianha...@gmail.com]

they are giving false commitment to the users about the fix date.

[Luc Bloom]

To circumvent Google AdMob taking our game over Google's Acceptable ANR Rate, I've created a simple system that can detect an ANR, report it to our backend and cleanly quits the app. I'm going to test it in the coming weeks and will report its effectiveness.

In the mean time, I'd like feedback on the idea and implementation from people who have also been dealing with this issue for years.

https://github.com/lucbloom/unity_anr_supervisor

[Mobile Ads SDK Forum Advisor]

Hi Luc,

Thank you for sharing this to us.

If you have any other concerns related to the implementation of Google Mobile Ads SDK, kindly provide us the details. We'll be happy to assist you.

Regards,

Princess Pamela Mobile Ads SDK Team

ref:_00D1U1174p._5004Q2atUiM:ref

[Mobile Ads SDK Forum Advisor]

Hi Anton,

Thank you for reaching out to us.

Do you have any concerns related to Mobile Ads SDK? If so, please provide us the details. We'll be happy to assist you.

[Roman]

Hello

Where is the fix?

Now ETA is November?

[Roman]

Dear Admob team,

Why don't you team up with Google Play to create a fix for Google Play which would filter out YOUR BUGS from counting towards apps' ANR rate, if you're unable to fix these bugs for already 8 months?

[Roman]

One more proof that all these ANRs caused directly by Admob is that in Belorussia and Russia where ads stopped serving since March (due to sanctions) ANR rate dropped to 0%-0.02%, despite lots of sessions.

[Bog]

Hello
Where is the promised fix?

[tonyev...@gmail.com]

Extremely disappointed, such a big company, the answer is so casual, please face the problem, don't prevaricate users, Admob's reputation has since declined!

[Mobile Ads SDK Forum Advisor]

Hello all,

Google Mobile Ads SDK version 21.0.0 is now available.

We have added manifest flags to optimize initialization and ad loading, please see Optimize initialization and ad loading guide for more details.

[Roman]

Great! Thank you,

Waiting for the Unity update, hopefully ANRs will be gone

[Dino Go]

Our latest game version live 4 hours ago( use admob 21.0.0). It seem working well. No anr report till now

[Dino Go]

Update stats. 21.1.0 reduce anr but not much. About 20%. Still get high anr report...

[Dino Go]

This is report for version 21.0.0. It is 0.64%, above bad threshold. So unsatisfied. I dont know how many year i must waiting for fixed  version