"main" prio=5 tid=1 Native
| group="main" sCount=1 dsCount=0 obj=0x73a85000 self=0xb8fddfa8
| sysTid=19430 nice=-4 cgrp=default sched=0/0 handle=0xb6fd8bec
| state=S schedstat=( 1092515842 330770336 1728 ) utm=58 stm=51 core=0 HZ=100
| stack=0xbe6cd000-0xbe6cf000 stackSize=8MB
| held mutexes=
#00 pc 000000000003a6b0 /system/lib/libc.so (__ioctl+8)
#01 pc 000000000003f829 /system/lib/libc.so (ioctl+14)
#02 pc 000000000001cb3b /system/lib/libbinder.so (android::IPCThreadState::talkWithDriver(bool)+138)
#03 pc 000000000001d147 /system/lib/libbinder.so (android::IPCThreadState::waitForResponse(android::Parcel*, int*)+42)
#04 pc 000000000001d2e9 /system/lib/libbinder.so (android::IPCThreadState::transact(int, unsigned int, android::Parcel const&, android::Parcel*, unsigned int)+124)
#05 pc 00000000000185c3 /system/lib/libbinder.so (android::BpBinder::transact(unsigned int, android::Parcel const&, android::Parcel*, unsigned int)+30)
#06 pc 00000000000841eb /system/lib/libandroid_runtime.so (???)
#07 pc 0000000000d36755 /system/framework/arm/boot.oat (Java_android_os_BinderProxy_transactNative__ILandroid_os_Parcel_2Landroid_os_Parcel_2I+144)
at android.os.BinderProxy.transactNative (BinderProxy.java)
at android.os.BinderProxy.transact (BinderProxy.java:496)
at android.os.IUserManager$Stub$Proxy.getApplicationRestrictions (IUserManager.java:817)
at android.os.UserManager.getApplicationRestrictions (UserManager.java:1311)
at org.chromium.policy.AppRestrictionsProvider.getApplicationRestrictions (AppRestrictionsProvider.java:7)
at org.chromium.policy.AbstractAppRestrictionsProvider.refresh (AbstractAppRestrictionsProvider.java:14)
at org.chromium.policy.CombinedPolicyProvider.linkNative (CombinedPolicyProvider.java:9)
at org.chromium.content.browser.BrowserStartupController.nativeFlushStartupTasks (BrowserStartupController.java)
at org.chromium.content.browser.BrowserStartupController.flushStartupTasks (BrowserStartupController.java:10)
at org.chromium.android_webview.AwBrowserProcess$$Lambda$0.run (AwBrowserProcess.java:56)
at org.chromium.base.ThreadUtils.runOnUiThreadBlocking (ThreadUtils.java:10)
at com.android.webview.chromium.WebViewChromiumAwInit.startChromiumLocked (WebViewChromiumAwInit.java:63)
at com.android.webview.chromium.WebViewChromiumAwInit.ensureChromiumStartedLocked (WebViewChromiumAwInit.java:135)
at com.android.webview.chromium.WebViewChromiumAwInit.startYourEngines (WebViewChromiumAwInit.java:116)
- locked <@addr=0x1313e610> (a java.lang.Object)
at com.android.webview.chromium.WebViewChromiumFactoryProvider.startYourEngines (WebViewChromiumFactoryProvider.java:149)
at com.android.webview.chromium.WebViewChromium.init (WebViewChromium.java:34)
at android.webkit.WebView.<init> (WebView.java:554)
at android.webkit.WebView.<init> (WebView.java:489)
at android.webkit.WebView.<init> (WebView.java:472)
at android.webkit.WebView.<init> (WebView.java:459)
at android.webkit.WebView.<init> (WebView.java:449)
at com.google.android.gms.ads.internal.webview.u.<init> (u.java:1)
at com.google.android.gms.ads.internal.webview.q.call (q.java:5)
at com.google.android.gms.ads.internal.util.bs.a (bs.java:23)
at com.google.android.gms.ads.internal.webview.o.a (o.java:8)
at com.google.android.gms.ads.internal.js.q.<init> (q.java:7)
at com.google.android.gms.ads.internal.js.z.run (z.java:5)
at com.google.android.gms.ads.internal.util.future.ad.execute (ad.java:4)
at com.google.android.gms.ads.internal.js.y.a (y.java:17)
at com.google.android.gms.ads.internal.js.y.a (y.java:27)
- locked <@addr=0x12c0a0d0> (a java.lang.Object)
at com.google.android.gms.ads.internal.js.function.b.b (b.java:4)
at com.google.android.gms.ads.internal.ac.a (ac.java:55)
at com.google.android.gms.ads.internal.ac.a (ac.java:4)
at com.google.android.gms.ads.internal.ax.a (ax.java:55)
at com.google.android.gms.ads.internal.client.bc.onTransact (bc.java:42)
at android.os.Binder.transact (Binder.java:380)
at com.google.android.gms.internal.ads.zzej.transactAndReadExceptionReturnVoid (zzej.java)
at com.google.android.gms.internal.ads.zzll.zza (zzll.java)
at com.google.android.gms.internal.ads.zzmb.zza (zzmb.java)
- locked <@addr=0x12c0a110> (a java.lang.Object)
at com.google.android.gms.ads.MobileAds.initialize (MobileAds.java)
at com.google.android.gms.ads.MobileAds.initialize (MobileAds.java)
Could you try our sample apps and see if you still experience same issue?
Y7 (HWTRT-Q) | 65 | 13,1% |
P9 lite (HWVNS-H) | 62 | 12,5% |
P8 lite 2017 (HWPRA-H) | 47 | 9,5% |
HUAWEI Y7 Prime 2018 (HWLDN-Q) | 45 | 9,1% |
Mate 10 lite (HWRNE) | 33 | 6,7% |
P10 lite (HWWAS-H) | 28 | 5,7% |
Honor 6A (HWDLI-Q) | 20 | 4,0% |
GT3 (HWNMO-H) | 16 | 3,2% |
MediaPad T3 7 (HWBG2) | 14 | 2,8% |
P9 Plus (HWVIE) | 11 | 2,2% |
v173_zkd_2f2 | 10 | 2,0% |
荣耀畅玩7X (HWBND-H) | 10 | 2,0% |
HUAWEI Y6 2018 (HWATU-QG) | 9 | 1,8% |
荣耀9青春版 (HWLLD-H) | 7 | 1,4% |
FIG-LX1 (HWFIG-H) | 7 | 1,4% |
荣耀畅玩 6X (HWBLN-H) | 7 | 1,4% |
3632A-mpcs (cp3632a) | 6 | 1,2% |
Moto G (2nd Gen) (titan_udstv) | 6 | 1,2% |
E (E) | 5 | 1,0% |
Galaxy J1 Mini Prime (j1minive3g) | 4 | 0,8% |
--
---
You received this message because you are subscribed to the Google Groups "Google Mobile Ads SDK Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-admob-ads-sdk+unsub...@googlegroups.com.
To post to this group, send email to google-admob-ads-sdk@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-admob-ads-sdk/0329ba71-1c00-4dee-af77-b2d350f89835%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Updated to the last version (3.15.0) and still getting the same ANRs. It's very frustrating :( We are thinking about replacing AdMob with UnityAds although the eCPM is lower, we can't reach the 99.9% free of ANRs with this problem
El lunes, 23 de julio de 2018, 20:56:25 (UTC+2), mobileadssdk-a...@google.com escribió:
Hi Juan,Our team is investigating the issue. But can you please confirm that you are seeing the issue on the latest version of SDK? I will also make sure to update you via this thread as soon as I have any new information from the team.Regards,Deepika UragayalaMobile Ads SDK Team=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~Also find us on our blog and Google+ page:
http://googleadsdeveloper.blogspot.com
https://plus.google.com/115658573333388777174/
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
On 07/20/18 17:34:12 jmcla...@gmail.com wrote:
Hi there.
Is there any news about this?
I am aware that the error is being investigated but more and more threads of users with the same problem appear in the group.
The biggest drawback of this error is that it is affecting too much the KPIs of "Android Vitals", also to have the right KPIs again, you have to wait 60 days since the problem is solved (Android Vitals takes the last 60 days reports).
Is there anything we could do to help solving this?
Thanks in advance
--
---
You received this message because you are subscribed to the Google Groups "Google Mobile Ads SDK Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-admob-ads-sdk+unsubscrib...@googlegroups.com.
To post to this group, send email to google-admob-ads-sdk@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-admob-ads-sdk/0329ba71-1c00-4dee-af77-b2d350f89835%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
--
---
You received this message because you are subscribed to the Google Groups "Google Mobile Ads SDK Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-admob-ads-sdk+unsub...@googlegroups.com.
To post to this group, send email to google-admob-ads-sdk@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-admob-ads-sdk/17c0aa20-1ee8-4988-a53e-e714b8d46475%40googlegroups.com.
Here it is:
To view this discussion on the web visit https://groups.google.com/d/msgid/google-admob-ads-sdk/17c0aa20-1ee8-4988-a53e-e714b8d46475%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
--
---
You received this message because you are subscribed to the Google Groups "Google Mobile Ads SDK Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-admob-ads-sdk+unsub...@googlegroups.com.
To post to this group, send email to google-admob-ads-sdk@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-admob-ads-sdk/1e5568ca-a279-4bc1-9916-b8a43b0f0d07%40googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-admob-ads-sdk/1e5568ca-a279-4bc1-9916-b8a43b0f0d07%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
--
---
You received this message because you are subscribed to the Google Groups "Google Mobile Ads SDK Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-admob-ads-sdk+unsub...@googlegroups.com.
To post to this group, send email to google-admob-ads-sdk@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-admob-ads-sdk/508ebd4c-672a-45db-a7d9-a2efbfdb6c31%40googlegroups.com.
Hi Giru,
Thank you for reaching out to us.
This seems to be more of a concern with Android WebView than with the AdMob SDK, judging by the stack trace (i.e. WebView occupies the few latest lines in the trace). Could you kindly try the following to see if it would alleviate the issue?
WebView webView = new WebView(this);
MobileAds.initialize(...);
|
||||||
Hi Giru,
To clarify, the AdMob SDK initializes WebView for ad-displaying purposes and, as per the stack trace you provided, it is WebView that is causing the ANR, not AdMob. The code snippet I provided should initialize WebView separately from AdMob, which should help in determining whether it is was WebView or AdMob that was truly causing the ANRs.
Hi Muhammad,
Thank you for reaching out to us.
Could you please provide the following details via Reply privately to author option or send it directly to mobileads...@gmail.com?
Regards,
|
||||||
Hi Oleg,
Thank you for reaching out to us.
Could you please provide the following details via Reply privately to author option or send it directly to mobileads...@gmail.com?
Hi Oleg,
Thank you for providing additional information to us.
Upon checking, we received reports from other publishers which seems to be the same issue as this one. However, this issue seems to be a result of WebView.init() rather than the MobileAds.initialize(). As suggestion by the team, could you please try running the following code snippet and see if that would solve the issue on your end?
WebView webView = new WebView(this);
MobileAds.initialize(...);
Regards,
Hello,
Thank you for reaching out to us.
Have you tried Optimize initialization and ad loading to fix the issue? If the issue still persists, kindly provide us the following information below privately for us to properly troubleshoot your issue:
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
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,
|
||||||