High ANRs rate in apps

[Fred]

We are noticing an increase of ANRs in our apps, most logs are related with Google Mediation, like this log below:

 #00 pc 00000000000a0078 /apex/com.android.runtime/lib/bionic/libc.so (__ioctl+8) #00 pc 000000000006c2f3 /apex/com.android.runtime/lib/bionic/libc.so (ioctl+26) #00 pc 000000000003a2c7 /system/lib/libbinder.so (android::IPCThreadState::talkWithDriver(bool)+218) #00 pc 000000000003b215 /system/lib/libbinder.so (android::IPCThreadState::waitForResponse(android::Parcel*, int*)+32) #00 pc 000000000003afdb /system/lib/libbinder.so (android::IPCThreadState::transact(int, unsigned int, android::Parcel const&, android::Parcel*, unsigned int)+122) #00 pc 00000000000356bf /system/lib/libbinder.so (android::BpBinder::transact(unsigned int, android::Parcel const&, android::Parcel*, unsigned int)+98) #00 pc 00000000000ce517 /system/lib/libandroid_runtime.so (android_os_BinderProxy_transact(_JNIEnv*, _jobject*, int, _jobject*, _jobject*, int)+82) at android.os.BinderProxy.transactNative (Native method) at android.os.BinderProxy.transact (BinderProxy.java:605) at android.content.ContentProviderProxy.query (ContentProviderNative.java:470) at android.content.ContentResolver.query (ContentResolver.java:1193) at android.content.ContentResolver.query (ContentResolver.java:1125) at android.content.ContentResolver.query (ContentResolver.java:1081) at com.google.android.gms.dynamite.DynamiteModule.zzc (unavailable:122) at com.google.android.gms.dynamite.DynamiteModule.zza (unavailable:96) at com.google.android.gms.dynamite.DynamiteModule.getRemoteVersion (unavailable:149) at com.google.android.gms.internal.ads.zzwd.zzd at com.google.android.gms.internal.ads.zzyu.zza at com.google.android.gms.ads.InterstitialAd.loadAd at com.applovin.mediation.adapters.GoogleMediationAdapter.loadInterstitialAd (GoogleMediationAdapter.java:152) at com.applovin.impl.mediation.j$6.run (unavailable) at com.applovin.impl.mediation.j$10.run (unavailable) at com.applovin.impl.mediation.j$5.run (unavailable) at android.os.Handler.handleCallback (Handler.java:938) at android.os.Handler.dispatchMessage (Handler.java:99) at android.os.Looper.loop (Looper.java:246) at android.app.ActivityThread.main (ActivityThread.java:8633) 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)

This is an intermittent error as you can see ahead, maybe because of the network mediation.

Do you have any idea what's happening ?

[Mobile Ads SDK Forum Advisor]

Hello,

For us to further investigate this, could you please provide the following details?

• Sample app
• Steps to replicate
• SDK Version Used
• Devices affected
• Percentage occurrence of the crash 

Kindly share the requested details via Reply to author option. If the option does not work, kindly reply to mobileadstesting99@gmail.com, then let us know here once sent.

Regards,

Teejay Wennie Pimentel Mobile Ads SDK Team

ref:_00D1U1174p._5004Q2SdiQp:ref

[Andrei Timofeev]

We are having a lot of similar ANR reports.

Input dispatching timed out (com.mobirate.DeadAheadTactics/com.mobirate.DeadAheadTactics.ExtendedUnityPlayerActivity, 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: 4. Wait queue head age: 8678.3ms.)

"main" prio=5 tid=1 Native

...

  at android.os.BinderProxy.transact (BinderProxy.java:605)
  at android.content.ContentProviderProxy.query (ContentProviderNative.java:470)

...

  at com.google.android.gms.dynamite.DynamiteModule.getRemoteVersion

...

  at com.google.android.gms.ads.rewarded.RewardedAd.load

  at com.ironsource.adapters.admob.AdMobAdapter.loadRewardedVideoAdFromAdMob (AdMobAdapter.java:323)

39 full ANR reports are attached in ANRs.zip.

Sample app: https://play.google.com/store/apps/details?id=com.mobirate.DeadAheadTactics&hl=en&gl=US

Steps to replicate: Install an app. Play until there is an option to view an ad in exchange for coins. Tap a button to load and watch an AdMob ad.

SDK version used: IronSource Unity SDK 7.1.11 with Admob Android SDK 20.2.0.

Devices affected: at least 34 models, Android 9, 10, 11, full list is attached (Devices.csv).

Percentage occurrence of the crash: not applicable, this is ANR, not a crash.

On Friday, December 10, 2021 at 10:01:43 AM UTC+4 mobileadssdk wrote:

Hello,

For us to further investigate this, could you please provide the following details?

• Sample app
• Steps to replicate
• SDK Version Used
• Devices affected
• Percentage occurrence of the crash 

Kindly share the requested details via Reply to author option. If the option does not work, kindly reply to mobileads...@gmail.com, then let us know here once sent.

[Andrei Timofeev]

Attachments:

[Andrei Timofeev]

From the stacktrace we can see that com.google.android.gms.ads.rewarded.RewardedAd.load calls ContentResolver.query from the main thread.

However ContentResolver's documentation notes that it should be called from a background thread.

https://developer.android.com/guide/topics/providers/content-provider-basics#SimpleQuery

"For the sake of clarity, the code snippets in this section call ContentResolver.query() on the UI thread. In actual code, however, you should do queries asynchronously on a separate thread."

[Mobile Ads SDK Forum Advisor]

Hi Andrei,

Thank you for reporting this. The team is currently reporting the issue. We'll let you know the soonest we have our findings.

[chotib]

Hello,

Is there any news about this ? we faced similar issue.

Regards,

Chotib

[Mobile Ads SDK Forum Advisor]

Hi Chotib,

Thank you for reaching out to us.

Can you provide us the following items below so that we can add it for additional information for investigation? You can send it 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.

• Full ANR logs
• Devices and version affected
• SDK version used

Regards,

Princess Pamela Pineda Mobile Ads SDK Team

ref:_00D1U1174p._5004Q2SdiQp:ref

[chotib]

Hello,

We are using Iron Source SDK v7.1.11.1 with admob v4.3.32.2 and here is the log : 
#00 pc 000000000007c9b8 /system/lib64/libc.so (__ioctl+4) #00 pc 000000000002c8f0 /system/lib64/libc.so (ioctl+132) #00 pc 000000000005cd88 /system/lib64/libbinder.so (android::IPCThreadState::talkWithDriver(bool)+244) #00 pc 000000000005db34 /system/lib64/libbinder.so (android::IPCThreadState::waitForResponse(android::Parcel*, int*)+60) #00 pc 000000000005d988 /system/lib64/libbinder.so (android::IPCThreadState::transact(int, unsigned int, android::Parcel const&, android::Parcel*, unsigned int)+176) #00 pc 00000000000519a0 /system/lib64/libbinder.so (android::BpBinder::transact(unsigned int, android::Parcel const&, android::Parcel*, unsigned int)+72) #00 pc 0000000000136c50 /system/lib64/libandroid_runtime.so (android_os_BinderProxy_transact(_JNIEnv*, _jobject*, int, _jobject*, _jobject*, int)+152) at android.os.BinderProxy.transactNative (Native method) at android.os.BinderProxy.transact (Binder.java:1129) at android.content.ContentProviderProxy.query (ContentProviderNative.java:416) at android.content.ContentResolver.query (ContentResolver.java:804) at android.content.ContentResolver.query (ContentResolver.java:753) at android.content.ContentResolver.query (ContentResolver.java:711) at com.google.android.gms.dynamite.DynamiteModule.zzb at com.google.android.gms.dynamite.DynamiteModule.zza at com.google.android.gms.dynamite.DynamiteModule.getRemoteVersion at com.google.android.gms.internal.ads.zzbax.zzd at com.google.android.gms.internal.ads.zzbaw.zzf at com.google.android.gms.ads.rewarded.RewardedAd.load at com.ironsource.adapters.admob.AdMobAdapter.loadRewardedVideoAdFromAdMob (AdMobAdapter.java:323) at com.ironsource.adapters.admob.AdMobAdapter.onNetworkInitCallbackSuccess (AdMobAdapter.java:932) at com.ironsource.adapters.admob.AdMobAdapter.initializationSuccess (AdMobAdapter.java:902) at com.ironsource.adapters.admob.AdMobAdapter.initSDK (AdMobAdapter.java:199) at com.ironsource.adapters.admob.AdMobAdapter.access$300 (AdMobAdapter.java:65) at com.ironsource.adapters.admob.AdMobAdapter$3.run (AdMobAdapter.java:260) at android.os.Handler.handleCallback (Handler.java:873) at android.os.Handler.dispatchMessage (Handler.java:99) at android.os.Looper.loop (Looper.java:280) at android.app.ActivityThread.main (ActivityThread.java:6706) at java.lang.reflect.Method.invoke (Native method) at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run (RuntimeInit.java:493) at com.android.internal.os.ZygoteInit.main (ZygoteInit.java:858)

For device affected : 
- Samsung Galaxy A52 5G

- Samsung Galaxy A51
- Samsung Galaxy A02s

Mostly occurs in device with Android 11 and Android 10

[Mobile Ads SDK Forum Advisor]

Hello,

Thank you for sharing with us those logs and the screenshot of the affected devices.

Allow me to share this additional information with the team. Rest assured that we will be updating this thread for any available information.

Regards,

Mark Kevin Albios Mobile Ads SDK Team

ref:_00D1U1174p._5004Q2SdiQp:ref

[Carlos Buraca]

Hello,

Are there any updates on this?

We are facing similar ANR issues in our clients, increasing in the last days.

The stack trace:

main (waiting): tid=1 systid=958
#00 pc 0x86b8c libc.so
#01 pc 0x1b092c libart.so
#02 pc 0x28e86c libart.so
#03 pc 0x2a5a60 libart.so
#04 pc 0x299050 libart.so
#05 pc 0x49315c libart.so
#06 pc 0x3e33b4 libart.so
#07 pc 0x119388 libandroid_runtime.so
       at android.os.Parcel.nativeReadString16(Parcel.java)
       at android.os.Parcel.readString16NoHelper(Parcel.java:2471)
       at android.os.Parcel$ReadWriteHelper.readString16(Parcel.java:413)
       at android.os.Parcel.readString16(Parcel.java:2450)
       at android.os.Parcel.createString16Array(Parcel.java:1483)
       at android.os.Parcel.readStringArray(Parcel.java:2712)
       at android.database.BulkCursorDescriptor.readFromParcel(BulkCursorDescriptor.java:71)
       at android.database.BulkCursorDescriptor$1.createFromParcel(BulkCursorDescriptor.java:34)
       at android.database.BulkCursorDescriptor$1.createFromParcel(BulkCursorDescriptor.java:30)
       at android.content.ContentProviderProxy.query(ContentProviderProxy.java:475)
       at android.content.ContentResolver.query(ContentResolver.java:1193)
       at android.content.ContentResolver.query(ContentResolver.java:1125)
       at android.content.ContentResolver.query(ContentResolver.java:1081)
       at com.google.android.gms.dynamite.DynamiteModule.zzc(DynamiteModule.java:174)
       at com.google.android.gms.dynamite.DynamiteModule.zza(DynamiteModule.java:116)
       at com.google.android.gms.dynamite.DynamiteModule.getRemoteVersion(DynamiteModule.java:204)
       at com.google.android.gms.internal.ads.zzwt.zzd(zzwt.java:43)
       at com.google.android.gms.internal.ads.zzzn.zza(zzzn.java:99)
       at com.google.android.gms.ads.admanager.AdManagerAdView.loadAd(AdManagerAdView.java:22)
       at org.greenrobot.eventbus.EventBus.invokeSubscriber(EventBus.java:507)
       at org.greenrobot.eventbus.EventBus.postToSubscription(EventBus.java:430)
       at org.greenrobot.eventbus.EventBus.postSingleEventForEventType(EventBus.java:411)
       at org.greenrobot.eventbus.EventBus.postSingleEvent(EventBus.java:384)
       at org.greenrobot.eventbus.EventBus.post(EventBus.java:265)
       at com.schibsted.scm.nextgenapp.hydra.HydraBinder.createTraceablePublisherAdView(HydraBinder.java:154)
       at com.schibsted.scm.nextgenapp.hydra.HydraBinder.access$createTraceablePublisherAdView(HydraBinder.java:34)
       at com.schibsted.scm.nextgenapp.hydra.HydraBinder$adView$2.invoke(HydraBinder.java:72)
       at com.schibsted.scm.nextgenapp.hydra.HydraBinder$adView$2.invoke(HydraBinder.java:34)
       at kotlin.SynchronizedLazyImpl.getValue(SynchronizedLazyImpl.java:74)
       at com.schibsted.scm.nextgenapp.hydra.HydraBinder.getAdView(HydraBinder.java)
       at com.schibsted.scm.nextgenapp.hydra.HydraBinder.bind$NextgenAndroidApp_release(HydraBinder.java:80)
       at com.schibsted.scm.nextgenapp.hydra.HydraInjector.injectAt(HydraInjector.java:62)
       at com.schibsted.scm.nextgenapp.hydra.RCTDFPView.startDFPRequest$NextgenAndroidApp_release(RCTDFPView.java:48)
       at com.schibsted.scm.nextgenapp.hydra.DFPViewReactManager.receiveCommand(DFPViewReactManager.java:44)
       at com.schibsted.scm.nextgenapp.hydra.DFPViewReactManager.receiveCommand(DFPViewReactManager.java:11)
       at com.facebook.react.uimanager.NativeViewHierarchyManager.dispatchCommand(NativeViewHierarchyManager.java:831)
       at com.facebook.react.uimanager.UIViewOperationQueue$DispatchCommandOperation.executeWithExceptions(UIViewOperationQueue.java:323)
       at com.facebook.react.uimanager.UIViewOperationQueue$1.run(UIViewOperationQueue.java:879)
       at com.facebook.react.uimanager.UIViewOperationQueue.flushPendingBatches(UIViewOperationQueue.java:1026)
       at com.facebook.react.uimanager.UIViewOperationQueue.access$2600(UIViewOperationQueue.java:47)
       at com.facebook.react.uimanager.UIViewOperationQueue$DispatchUIFrameCallback.doFrameGuarded(UIViewOperationQueue.java:1086)
       at com.facebook.react.uimanager.GuardedFrameCallback.doFrame(GuardedFrameCallback.java:29)
       at com.facebook.react.modules.core.ReactChoreographer$ReactChoreographerDispatcher.doFrame(ReactChoreographer.java:175)
       at com.facebook.react.modules.core.ChoreographerCompat$FrameCallback$1.doFrame(ChoreographerCompat.java:85)
       at android.view.Choreographer$CallbackRecord.run(Choreographer.java:1008)
       at android.view.Choreographer.doCallbacks(Choreographer.java:809)
       at android.view.Choreographer.doFrame(Choreographer.java:740)
       at android.view.Choreographer$FrameDisplayEventReceiver.run(Choreographer.java:995)
       at android.os.Handler.handleCallback(Handler.java:938)
       at android.os.Handler.dispatchMessage(Handler.java:99)
       at android.os.Looper.loop(Looper.java:246)
       at android.app.ActivityThread.main(ActivityThread.java:8633)
       at java.lang.reflect.Method.invoke(Method.java)
       at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:602)
       at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1130)

We use Google Play Services 20.5 and the SDK 31.

Devices affected (mostly Android 11):

70% Samsung

20% Motorola

8% Xiaomi

2% Others

Thanks.

Regards.

[Mobile Ads SDK Forum Advisor]

Hi all,

Thank you for your patience. Please be informed that the team is currently on the testing and evaluation phase for the aforementioned fix. I'll update this thread as soon as the fix has been released.

Regards,

Teejay Wennie Pimentel Mobile Ads SDK Team

ref:_00D1U1174p._5004Q2SdiQp:ref

[Mobile Ads SDK Forum Advisor]

Hi All,

I hope you're doing well.

I just want to circle back on this. Feel free to come back to us if you still encounter any issues regarding this.

Regards,

Princess Pamela Mobile Ads SDK Team

 

ref:_00D1U1174p._5004Q2SdiQp:ref

[byte...@gmail.com]

Hello,

to the Mobile Ads SDK team: did the issue get fixed?

to everyone else: did someone find a solution?

We also had a high rate of ANRs caused by Admob and have recently removed it from our app. ANRs dropped significantly.

Greetings,

Gerhard

[Mobile Ads SDK Forum Advisor]

Hi Gerhard,

Thank you for reaching out to us.

 Since you mentioned that you are encountering this ANR also, can you provide us the following details below?

• Sample app project(if any)
• Full stack trace
• Device name and versions affected
• SDK version

If the file(s) you are looking to share are less than 25mb in total you can attach them to this case on your next reply. If you are having trouble attaching your file to this case or if your file(s) are larger than 25mb, you can share your files with me by performing the following steps:

1. Navigate to https://docs.google.com/forms/d/e/1FAIpQLSfkAiXMeYP-fw1W3Z-tT9uwmATEKO5X6S-th0gR2ezdKaaqfg/viewform?usp=pp_url&entry.400550049=Mobile+Ads+SDK&entry.460850823=5004Q00002SdiQpQAJ&entry.80707362=00088369
2. Fill out all fields, and attach your file(s).
3. Please reply back on this thread when you have uploaded your file(s). Please do not share this link.

[Stefan Wiese]

Hi,

one of our clients is getting similar or the same kind of ANRs after a recent update. Please see the stack traces for used versions.

As mentioned in a message above the ContentResolver.query() on the main thread may be causing this, and somewhere else someone mentioned he could trigger similar ANRs by clearing the cache of Play Services app and the starting the affected app. (Cannot confirm this, as we did not test it yet.)

Can you maybe shed some light on the general situation for the observed stack traces? Which kind of information and component is causing the delay here. Is it Google Ads SDK is trying to obtain information from Play Services (outside of app)?

Here our traces:

android.os.BinderProxy.transactNative (BinderProxy.java)

android.os.BinderProxy.transact (BinderProxy.java:593)

android.content.ContentProviderProxy.query (ContentProviderProxy.java:470)

android.content.ContentResolver.query (ContentResolver.java:1195)

android.content.ContentResolver.query (ContentResolver.java:1127)

android.content.ContentResolver.query (ContentResolver.java:1083)

com.google.android.gms.dynamite.DynamiteModule.zzb (com.google.android.gms:play-services-basement@@18.1.0:10)

com.google.android.gms.dynamite.DynamiteModule.zza (com.google.android.gms:play-services-basement@@18.1.0:47)

com.google.android.gms.dynamite.DynamiteModule.getRemoteVersion (com.google.android.gms:play-services-basement@@18.1.0:1)

com.google.android.gms.ads.internal.client.zzax.zzd (com.google.android.gms:play-services-ads-lite@@21.5.0:5)

com.google.android.gms.ads.internal.client.zzea.zzm (com.google.android.gms:play-services-ads-lite@@21.5.0:11)

com.google.android.gms.ads.admanager.AdManagerAdView.loadAd (com.google.android.gms:play-services-ads-lite@@21.5.0:5)

...

and/or:

android.os.BinderProxy.transactNative (BinderProxy.java)

android.os.BinderProxy.transact (BinderProxy.java:540)

android.app.IActivityManager$Stub$Proxy.refContentProvider (IActivityManager.java:5746)

android.app.ActivityThread.incProviderRefLocked (ActivityThread.java:6917)

android.app.ActivityThread.acquireExistingProvider (ActivityThread.java:6981)

android.app.ActivityThread.acquireProvider (ActivityThread.java:6840)

android.app.ContextImpl$ApplicationContentResolver.acquireProvider (ContextImpl.java:2911)

android.content.ContentResolver.acquireProvider (ContentResolver.java:2435)

android.content.ContentResolver.query (ContentResolver.java:1210)

android.content.ContentResolver.query (ContentResolver.java:1116)

android.content.ContentResolver.query (ContentResolver.java:1072)

com.google.android.gms.dynamite.DynamiteModule.zzb (com.google.android.gms:play-services-basement@@18.1.0:10)

com.google.android.gms.dynamite.DynamiteModule.zza (com.google.android.gms:play-services-basement@@18.1.0:47)

com.google.android.gms.dynamite.DynamiteModule.getRemoteVersion (com.google.android.gms:play-services-basement@@18.1.0:1)

com.google.android.gms.ads.internal.client.zzax.zzd (com.google.android.gms:play-services-ads-lite@@21.5.0:5)

com.google.android.gms.ads.internal.client.zzaw.zzc (com.google.android.gms:play-services-ads-lite@@21.5.0:2)

com.google.android.gms.ads.AdLoader$Builder.<init> (com.google.android.gms:play-services-ads-lite@@21.5.0:3)

...

[Mobile Ads SDK Forum Advisor]

Hi Stefan,

Thank you for reaching out to us.

With regard to the ANR you're experiencing, can you confirm if you already tried to use the Optimize initialization and ad loading guide? This will help you to 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. If you're not yet tried this, kindly try it and let us know if this help you with your ANR. If it still exist, kindly provide us additional information below for us to further check and provide more context with regard to your questions.

• SDK version

• Full stack trace
• Device name and versions affected

• Mediation adapter used (if any)

You can provide the following details via reply privately to author option or directly provide it to the link below.

If the file(s) you are looking to share are less than 25mb in total you can attach them to this case on your next reply. If you are having trouble attaching your file to this case or if your file(s) are larger than 25mb, you can share your files with me by performing the following steps:

1. Navigate to https://docs.google.com/forms/d/e/1FAIpQLSfkAiXMeYP-fw1W3Z-tT9uwmATEKO5X6S-th0gR2ezdKaaqfg/viewform?usp=pp_url&entry.400550049=Mobile+Ads+SDK&entry.460850823=5004Q00002SdiQpQAJ&entry.80707362=00088369

2. Fill out all fields, and attach your file(s).

3. Please reply back on this thread when you have uploaded your file(s). Please do not share this link.

Regards,

Mobile Ads SDK Team

ref:_00D1U1174p._5004Q2SdiQp:ref

[Stefan Wiese]

Thanks for the provided info, we'll consider to test the new Manifest entries. 

Besides that we are not able to provide much more information, SDK version should be 21.0.0.

Any chance to get a rough description of what kind of functionality the Google Ads SDK is dealing with (regarding the provided stack traces)? Would maybe help when trying to reproduce it.

Best,

Stefan

[Mobile Ads SDK Forum Advisor]

Hi Stefan,

Thank you for your response.

With regard to your question, we can't provide any specific with regard to the ANR you're encountering with the following stack traces you've provided since ANR has different causes. We are asking for additional information so that we can share it to the wider team for them to properly assess the following ANR. Then, for replicating it, if you're able to replicate it in your end, then we may be needing a steps to replicate for us to check it in our end. As mentioned previously, if you're not yet tried  to use the Optimize initialization and ad loading guide, kindly try it and let us know if this help you with your ANR. If it still exist, kindly provide us additional information below for us to further check and provide more context with regard to your questions.