googleads-mobile-unity Huge number of ANRs in Unity: Input dispatching timed out...

[REQUIRED] Step 1: Describe your environment

Unity version: 2020.3.18f1
Google Mobile Ads Unity plugin version: v6.1.0, v6.1.1
Platform: Android
Platform OS version: Android 6 - 10
Any specific devices issue occurs on: BQru BQ-4028UP!, Lenovo Tab M7, Nokia 5, ZTE Blade L130, Redmi 9C NFC, HOMTOM S16, Huawei 荣耀9青春版
Mediation ad networks used, and their versions: None

[REQUIRED] Step 2: Describe the problem

In past year Admob team introduced a bug into its Unity SDK which causes a huge number of ANRs for many developers. You can find lots of reports on support forum, but the most recent topic is https://groups.google.com/g/google-admob-ads-sdk/c/6LfTaInDGtU.

The issue seems to be a deadlock related to the init of the WebView. Initially Admob team ignored and and attributed the problem to a bug in a specific Android's WebView bug, and as they said issue should have recede as people upgrade to newer WebView. Turns out it's not the case, and we see more and more ANRs in a newer versions of Android. What even more suspicious these ANRs come in waves - few days there is none of them, and then huge wave which pushes apps to a bad behaviour threshold.

This problem is super critical, since i ruins many apps and business, because Google Play severely punishes apps for even slight increase in ANRs rate.

So far Admob team was handling this issue in a disgraceful way: ignoring it initially, and "investigating" it for about 2-3 months already with no result.

There is two types of ANRs related to the same issue:

1. Broadcast of Intent { act=android.intent.action.SCREEN_OFF flg=0x58200010 }

No stack trace

2. 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: 9. Wait queue head age: 14852.2ms.)
com.unity3d.player.UnityPlayerActivity

  #00  pc 00000000000706b4  /system/lib64/libc.so (nanosleep+8)
  #00  pc 000000000045b150  /data/app/com.app.id-3lXBPjkSmjrQATT-XgPpFg==/lib/arm64/libil2cpp.so (???)
  #00  pc 0000000000467d58  /data/app/com.app.id-3lXBPjkSmjrQATT-XgPpFg==/lib/arm64/libil2cpp.so (???)
  #00  pc 000000000047a010  /data/app/com.app.id-3lXBPjkSmjrQATT-XgPpFg==/lib/arm64/libil2cpp.so (???)
  #00  pc 000000000043bb3c  /data/app/com.app.id-3lXBPjkSmjrQATT-XgPpFg==/lib/arm64/libil2cpp.so (???)
  #00  pc 00000000002d42c0  /data/app/com.app.id-3lXBPjkSmjrQATT-XgPpFg==/lib/arm64/libunity.so (???)
  #00  pc 000000000017ad04  /data/app/com.app.id-3lXBPjkSmjrQATT-XgPpFg==/lib/arm64/libunity.so (???)
  #00  pc 000000000017ac1c  /data/app/com.app.id-3lXBPjkSmjrQATT-XgPpFg==/lib/arm64/libunity.so (???)
  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@[email protected]:2)
  at com.google.android.gms.ads.internal.initialization.f.e (com.google.android.gms.policy_ads_fdr_dynamite@[email protected])
  at com.google.android.gms.ads.nonagon.initialization.c.run (com.google.android.gms.policy_ads_fdr_dynamite@[email protected]: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@[email protected])
  at com.google.android.gms.ads.internal.util.f.a (com.google.android.gms.policy_ads_fdr_dynamite@[email protected]:1)
  at ato.dispatchMessage (com.google.android.gms.policy_ads_fdr_dynamite@[email protected])
  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)

Oct 23 '21 09:10 bogmix

Hi

Asma

From: bogmix @.> Sent: Saturday, October 23, 2021 2:29:34 PM To: googleads/googleads-mobile-unity @.> Cc: Subscribed @.***> Subject: [googleads/googleads-mobile-unity] Huge number of ANRs in Unity: Input dispatching timed out... (Issue #1825)

[REQUIRED] Step 1: Describe your environment

Unity version: 2020.3.18f1
Google Mobile Ads Unity plugin version: v6.1.0, v6.1.1
Platform: Android
Platform OS version: Android 6 - 10
Any specific devices issue occurs on: BQru BQ-4028UP!, Lenovo Tab M7, Nokia 5, ZTE Blade L130, Redmi 9C NFC, HOMTOM S16, Huawei 荣耀9青春版
Mediation ad networks used, and their versions: None

[REQUIRED] Step 2: Describe the problem

In past year Admob team introduced a bug into its Unity SDK which causes a huge number of ANRs for many developers. You can find lots of reports on support forum, but the most recent topic is https://groups.google.com/g/google-admob-ads-sdk/c/6LfTaInDGtU.

The issue seems to be a deadlock related to the init of the WebView. Initially Admob team ignored and and attributed the problem to a bug in a specific Android's WebView bug, and as they said issue should have recede as people upgrade to newer WebView. Turns out it's not the case, and we see more and more ANRs in a newer versions of Android. What even more suspicious these ANRs come in waves - few days there is none of them, and then huge wave which pushes apps to a bad behaviour threshold.

This problem is super critical, since i ruins many apps and business, because Google Play severely punishes apps for even slight increase in ANRs rate.

So far Admob team was handling this issue in a disgraceful way: ignoring it initially, and "investigating" it for about 2-3 months already with no result.

There is two types of ANRs related to the same issue:

Broadcast of Intent { act=android.intent.action.SCREEN_OFF flg=0x58200010 }

No stack trace

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: 9. Wait queue head age: 14852.2ms.)

com.unity3d.player.UnityPlayerActivity

#00 pc 00000000000706b4 /system/lib64/libc.so (nanosleep+8)

#00 pc 000000000045b150 /data/app/com.app.id-3lXBPjkSmjrQATT-XgPpFg==/lib/arm64/libil2cpp.so (???)

#00 pc 0000000000467d58 /data/app/com.app.id-3lXBPjkSmjrQATT-XgPpFg==/lib/arm64/libil2cpp.so (???)

#00 pc 000000000047a010 /data/app/com.app.id-3lXBPjkSmjrQATT-XgPpFg==/lib/arm64/libil2cpp.so (???)

#00 pc 000000000043bb3c /data/app/com.app.id-3lXBPjkSmjrQATT-XgPpFg==/lib/arm64/libil2cpp.so (???)

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

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

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

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 @.***@213806100057.397311113.397311113:2)

at com.google.android.gms.ads.internal.initialization.f.e @.***@213806100057.397311113.397311113)

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

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

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

at ato.a @.***@213806100057.397311113.397311113)

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

at ato.dispatchMessage @.***@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)

― You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHubhttps://github.com/googleads/googleads-mobile-unity/issues/1825, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AJAHSOEIW6OBDI2QVI3YN4DUIJ575ANCNFSM5GSCF2LQ. Triage notifications on the go with GitHub Mobile for iOShttps://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Androidhttps://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

Oct 25 '21 07:10 niceali

Asma

From: bogmix @.> Sent: Saturday, October 23, 2021 2:29:34 PM To: googleads/googleads-mobile-unity @.> Cc: Subscribed @.***> Subject: [googleads/googleads-mobile-unity] Huge number of ANRs in Unity: Input dispatching timed out... (Issue #1825)

[REQUIRED] Step 1: Describe your environment

Unity version: 2020.3.18f1
Google Mobile Ads Unity plugin version: v6.1.0, v6.1.1
Platform: Android
Platform OS version: Android 6 - 10
Any specific devices issue occurs on: BQru BQ-4028UP!, Lenovo Tab M7, Nokia 5, ZTE Blade L130, Redmi 9C NFC, HOMTOM S16, Huawei 荣耀9青春版
Mediation ad networks used, and their versions: None

[REQUIRED] Step 2: Describe the problem

In past year Admob team introduced a bug into its Unity SDK which causes a huge number of ANRs for many developers. You can find lots of reports on support forum, but the most recent topic is https://groups.google.com/g/google-admob-ads-sdk/c/6LfTaInDGtU.

The issue seems to be a deadlock related to the init of the WebView. Initially Admob team ignored and and attributed the problem to a bug in a specific Android's WebView bug, and as they said issue should have recede as people upgrade to newer WebView. Turns out it's not the case, and we see more and more ANRs in a newer versions of Android. What even more suspicious these ANRs come in waves - few days there is none of them, and then huge wave which pushes apps to a bad behaviour threshold.

This problem is super critical, since i ruins many apps and business, because Google Play severely punishes apps for even slight increase in ANRs rate.

So far Admob team was handling this issue in a disgraceful way: ignoring it initially, and "investigating" it for about 2-3 months already with no result.

There is two types of ANRs related to the same issue:

Broadcast of Intent { act=android.intent.action.SCREEN_OFF flg=0x58200010 }

No stack trace

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: 9. Wait queue head age: 14852.2ms.)