This binder call may be taking too long, causing the main thread to wait and triggering the ANR

[Muhammad Riaz]

This binder call may be taking too long, causing the main thread to wait and triggering the ANR

  at android.os.BinderProxy.transact (BinderProxy.java:510)
  at android.app.IUiModeManager$Stub$Proxy.getCurrentModeType (IUiModeManager.java:288)
  at android.app.UiModeManager.getCurrentModeType (UiModeManager.java:207)
  at com.google.android.gms.ads.omid.library.utils.a.a (:com.google.android.gms.policy_ads_fdr_dynamite@233012805@233012802057.555274289.555274289:5)
  at com.google.android.gms.ads.omid.library.processor.d.a (:com.google.android.gms.policy_ads_fdr_dynamite@233012805@233012802057.555274289.555274289:6)
  at com.google.android.gms.ads.omid.library.walking.e.run (:com.google.android.gms.policy_ads_fdr_dynamite@233012805@233012802057.555274289.555274289:321)
  at android.os.Handler.handleCallback (Handler.java:883)
  at android.os.Handler.dispatchMessage (Handler.java:100)
  at android.os.Looper.loop (Looper.java:224)
  at android.app.ActivityThread.main (ActivityThread.java:7519)
  at java.lang.reflect.Method.invoke (Native method)
  at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run (RuntimeInit.java:539)
  at com.android.internal.os.ZygoteInit.main (ZygoteInit.java:995)

[Mobile Ads SDK Forum Advisor]

Hi, 

Thank you for contacting the Mobile Ads SDK support team.

By reviewing your concern, I understand that you are facing ANR issues due to AdMob SDK. Kindly provide the below information for further investigation:

• Mobile Ads SDK Version
• Device/OS versions affected
• Sample project reproducing the issue

 

This message is in relation to case "ref:!00D1U01174p.!5004Q02pTqM6:ref"

Thanks,
 

Mobile Ads SDK Team

 

[Juan BLASCO]

How are we supposed to send a sample project reproducing the issue if this just happens to a certain percentage of our user base ??

Plus we are losing our feature in google play for a bug caused by your SDK,  you should seriously look into it.