ANR using Admob from Google Play Services

[Gert]

Hello,

I've just received an ANR report from a user. A closer look at the stack traces attached shows that the ANR occurs in an onDestroy method, that calls the destroy of an AdView.

The project is obfuscated using proguard, so it's not that easy to tell the exact method.

"main" prio=5 tid=1 MONITOR

| group="main" sCount=1 dsCount=0 obj=0x41d8bf80 self=0x41d785f0

| sysTid=6879 nice=0 sched=0/0 cgrp=apps handle=1073987200

| state=S schedstat=( 3859163490 373301317 3343 ) utm=287 stm=98 core=2

at wd.b(SourceFile:~275)

- waiting to lock <0x428bda30> (a java.lang.Object) held by tid=13 (AdWorker #3)

at xe.f(SourceFile:33)

at tj.p(SourceFile:522)

at tj.b(SourceFile:152)

at tt.onTransact(SourceFile:59)

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

at com.google.android.gms.internal.g.b((null):-1)

at com.google.android.gms.ads.f.a((null):-1)

at myApp.a.b((null):-1)

at myApp.myActivity.onDestroy((null):-1)

at android.app.Activity.performDestroy(Activity.java:5436)

at android.app.Instrumentation.callActivityOnDestroy(Instrumentation.java:1127)

at android.app.ActivityThread.performDestroyActivity(ActivityThread.java:3525)

at android.app.ActivityThread.handleDestroyActivity(ActivityThread.java:3556)

at android.app.ActivityThread.access$1300(ActivityThread.java:150)

at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1333)

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

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

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

at java.lang.reflect.Method.invokeNative(Native Method)

at java.lang.reflect.Method.invoke(Method.java:511)

at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:1102)

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

at dalvik.system.NativeStart.main(Native Method)

The code marked in yellow, tells me this is code from the Google Play Services library I link to. The code marked with green gives me a strong clue it has to do with the AdMob ads.

I've used the latest Android SDK Tools (22.3) and Google Play Services Library (revision 13)  to build this app using Eclipse.

Is there something I could do to prevent this?  (I cound skip calling destroy()). 

[Eric Leichtenschlag]

I was hoping we wouldn't see any traces of this in the Google Play services version :(

We'll investigate this issue. The trace is useful and it does point to the ads library unfortunately. It doesn't look like you're calling adView.destroy() yourself, but I don't think that'll solve the issue.
Do you have any additional information on how often this occurs, or what devices it happens on?

Thanks,
Eric

[Xavier]

Hello,

I have ANR problems too while using either the Play Services or older versions. After some debugging, I observed it always happens when finishing an activity which was currently looking for an ad.

I could force an ANR to happen every single time by launching a new activity and inmediately closing it while the library was requesting an ad from any of the mediation sources or Admob network. 

It would never happen when finishing the activity after the ad has been shown, or when finishing the activity before the library made the request for an ad (i.e setting a delay). 

To avoid this, the only solution I found is NOT calling adView.destroy() from the Activity onDestroy method.

[Xavier]

By older versions I mean 6.4.1 and maybe 6.4.0 too, I can't remember now, but not before, or at least not every single time.

[Gert]

Hello Eric,

So far, I've only had 2 ANR reported on about 75k requests. But those 2 occured a few hours after the update. Still I don't know how many users did not report a message.

I actually did call the destroy myself. The stacktrace below:

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

at com.google.android.gms.internal.g.b((null):-1)

at com.google.android.gms.ads.f.a((null):-1)

at myApp.a.b((null):-1)

at myApp.myActivity.onDestroy((null):-1)

at android.app.Activity.performDestroy(Activity.java:5436)

shows the call goes through method myApp.a.b. This is a wrapper to handle the ads in my app.

The cause might be: On some occasions, I start another activity in the onCreate. In the onCreate the AdMob ad is loaded, the ad is probably loading or initializing when the Activity is destroyed. Could it be the library cannot handle a loadAd and destroy, too soon after each other. If I look the response from Xavier, he is reporting the same.

Gert

[Christer Nordvik]

Any update on this? I saw a lot of complaints from our users about ANR and checked our logs and we have 306(!) ANR the last week. Almost all of them seem to point to the AdMob with similar stack trace as OP with the OnDestroy method calling the destroy of the ad. What happens if we remove the code in OnDestroy()?

"main" prio=5 tid=1 MONITOR
| group="main" sCount=1 dsCount=0 obj=0x40d7f978 self=0x4bd1e038
| sysTid=28222 nice=0 sched=0/0 cgrp=apps handle=1074342760
| schedstat=( 8420172079 77334129390 28401 ) utm=733 stm=109 core=1
at wd.b(SourceFile:~275)
- waiting to lock <0x415bc438> (a java.lang.Object) held by tid=29 (AdWorker #2)

at xe.f(SourceFile:33)
at tj.p(SourceFile:522)
at tj.b(SourceFile:152)
at tt.onTransact(SourceFile:59)

at android.os.Binder.transact(Binder.java:326)
at com.google.android.gms.internal.ac$a$a.destroy((null):-1)
at com.google.android.gms.ads.AdView.destroy((null):-1)
at com.myapp.BaseActivityV2.onDestroy(BaseActivityV2.java:572)
at com.myapp.MyActivity.onDestroy(MyActivity.java:1047)
at android.app.Activity.performDestroy(Activity.java:5185)
at android.app.Instrumentation.callActivityOnDestroy(Instrumentation.java:1111)
at android.app.ActivityThread.performDestroyActivity(ActivityThread.java:3428)
at android.app.ActivityThread.handleDestroyActivity(ActivityThread.java:3459)

[Eric Leichtenschlag]

We're still looking into this, but we can confirm it's an issue on our side. This crash could be avoided by not calling adView.destroy(), but there may be other issues with tearing down a WebView if you don't call this method.

Thanks,
Eric

[Christer Nordvik]

So you don't recommend us removing the adView.destroy() as a temporary fix? With 300 ANR's each week we really need either a quick fix (this issue was reported 2 weeks ago) or a workaround. 

[Eric Leichtenschlag]

If I was getting 300 crashes I'd still try this as a workaround. I remember adView.destroy() resolved some issues on older versions of Android, like 1.x issues. Since Google Play Services is 2.3 and up, 1.x is obviously no longer an issue. I just don't remember if there were still issues on 2.3 if adView.destroy() wasn't called.

[Christer Nordvik]

Ok thanks! I have removed the destroy and updated our app just now. Hopefully it will resolve it without causing a lot of other issues. Please keep us updated once a new SDK version is available that fixes this :-) 

[Christer Nordvik]

When looking through the ANR reports there are also reports of the same issue when loading an ad. Is this also a bug?

DALVIK THREADS:
(mutexes: tll=0 tsl=0 tscl=0 ghl=0 hwl=0 hwll=0)
"main" prio=5 tid=1 VMWAIT
| group="main" sCount=1 dsCount=0 obj=0x401d7188 self=0xcf80
| sysTid=20124 nice=0 sched=0/0 cgrp=default handle=-1345006336
| schedstat=( 1014191649 2053571245 1173 )
at dalvik.system.DexFile.openDexFile(Native Method)
at dalvik.system.DexFile.<init>(DexFile.java:103)
at dalvik.system.DexFile.loadDex(DexFile.java:142)
at dalvik.system.DexClassLoader.<init>(DexClassLoader.java:117)
at qa.a(SourceFile:87)
at qc.a(SourceFile:68)
at tk.<init>(SourceFile:97)
at tj.<init>(SourceFile:134)
at com.google.android.gms.ads.AdManagerCreatorImpl.newAdManager(SourceFile:34)
at tv.onTransact(SourceFile:66)
at android.os.Binder.transact(Binder.java:279)
at com.google.android.gms.internal.ad$a$a.a((null):-1)
at com.google.android.gms.internal.u.b((null):-1)
at com.google.android.gms.internal.u.a((null):-1)
at com.google.android.gms.ads.AdView.c((null):-1)
at com.google.android.gms.ads.AdView.loadAd((null):-1)
at com.myapp.util.GuiUtils.loadAdmobAds(GuiUtils.java:1229)
at com.myapp.util.GuiUtils.EnableAds2(GuiUtils.java:1113)
at com.myapp.gui.v2.BaseActivityV2.enableAds(BaseActivityV2.java:509)
at com.myapp.gui.v2.BaseActivityV2.onResume(BaseActivityV2.java:428)

[Bytra]

Hi,

Any news about this ANR? We have reported ANRs in the same place. 

[Christer Nordvik]

An update on this would be nice. Removing the code in OnDestroy seemed to help but we still have ANRs like this: 

"main" prio=5 tid=1 MONITOR
| group="main" sCount=1 dsCount=0 obj=0x4105c508 self=0x40f5f9a0
| sysTid=6633 nice=0 sched=0/0 cgrp=apps handle=1075380016
| schedstat=( 11797752843 23160060580 20830 ) utm=1048 stm=131 core=0
at wd.b(SourceFile:~275)
- waiting to lock <0x422ed528> (a java.lang.Object) held by tid=35 (AdWorker #2)

at xe.f(SourceFile:33)
at tj.p(SourceFile:522)
at tj.b(SourceFile:152)
at tt.onTransact(SourceFile:59)
at android.os.Binder.transact(Binder.java:326)
at com.google.android.gms.internal.ac$a$a.destroy((null):-1)
at com.google.android.gms.ads.AdView.destroy((null):-1)

at com.google.ads.mediation.admob.AdMobAdapter.destroy((null):-1)
at com.google.android.gms.internal.az.destroy((null):-1)
at com.google.android.gms.internal.ax$a.onTransact((null):-1)
at android.os.Binder.transact(Binder.java:326)
at vf.c(SourceFile:227)
at uq.run(SourceFile:93)
at android.os.Handler.handleCallback(Handler.java:615)
at android.os.Handler.dispatchMessage(Handler.java:92)
at android.os.Looper.loop(Looper.java:137)
at android.app.ActivityThread.main(ActivityThread.java:4921)

at java.lang.reflect.Method.invokeNative(Native Method)
at java.lang.reflect.Method.invoke(Method.java:511)

at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:1027)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:794)
at dalvik.system.NativeStart.main(Native Method)

[Christer Nordvik]

Can we get an update on this if possible? Have you found the issue? Will there be a new release soon?

[Bjørn Christian Seime]

Removing the destroy() call introduces a new crash issue in my app:

java.lang.IllegalArgumentException: Service not registered: ano@408db8b0

at android.app.LoadedApk.forgetServiceDispatcher(LoadedApk.java:891)

at android.app.ContextImpl.unbindService(ContextImpl.java:998)

at android.content.ContextWrapper.unbindService(ContextWrapper.java:352)

at ta.a(SourceFile:135)

at qc.d(SourceFile:88)

at qc.b(SourceFile:129)

at pz.a(SourceFile:239)

at pz.a(SourceFile:176)

at wd.a(SourceFile:112)

at xf.run(SourceFile:14)

at xh.run(SourceFile:30)

at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1088)

at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:581)

at java.lang.Thread.run(Thread.java:1019)

[Christer Nordvik]

Are you using Google Analytics? I thought this was their issue, but not sure. We have the same crashlogs in our app.  WE are now considering removing both AdMob and Google Analytics now since they don't respond either of them to bug reports. 

Google Analytics also have issues like this that they just seem to ignore: 

https://code.google.com/p/analytics-issues/issues/detail?id=378&sort=-id&colspec=ID%20Component%20Type%20Status%20Priority%20Stars%20Summary

I hope someone from Google can get onto this thread again so we can know what to do about this issue. 

[Eric Leichtenschlag]

The SDK engineers weren't able to reproduce this issue locally, but have analyzed the stack trace and are making a change that hoepfully fixes this. The bad news is that it going go out in next release that's starting to roll out. It'll be available in the following launch.

[Bjørn Christian Seime]

Yes, I am using Google Analytics too. Though I am pretty sure we did not receive this error when using the old Admob library in combination with Analytics.

[Ian Dixon]

I'm having the issue too. What is the official recommendation for an interim solution while we wait for a release? I've seen some suggestion of removing destroy() but I'm wary of introducing another problem. I'm able to recreate an ANR frequently on my test devices.

DALVIK THREADS:
(mutexes: tll=0 tsl=0 tscl=0 ghl=0)

"main" prio=5 tid=1 MONITOR
| group="main" sCount=1 dsCount=0 obj=0x41bf7e40 self=0x41be6818
| sysTid=9159 nice=-6 sched=0/0 cgrp=apps handle=1073926484
| state=S schedstat=( 0 0 0 ) utm=1922 stm=267 core=0
at wd.b(SourceFile:~275)
- waiting to lock <0x424af378> (a java.lang.Object) held by tid=20 (AdWorker #3)

at xe.f(SourceFile:33)
at tj.p(SourceFile:522)
at tj.b(SourceFile:152)
at tt.onTransact(SourceFile:59)

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

[Eric Leichtenschlag]

I'm afraid we don't have a workaround at this time. If you already implemented mediation, you may consider sending requests elsewhere for now to reduce the ANR count (this looks to be an AdMob network issue, not an issue with the mediation layer).

Thanks,
Eric

[sreeni vasan]

I'm having the issue too.

JNI: CheckJNI is off; workarounds are off; pins=0; globals=325 (plus 136 weak)

DALVIK THREADS:
(mutexes: tll=0 tsl=0 tscl=0 ghl=0)

"main" prio=5 tid=1 MONITOR

  | group="main" sCount=1 dsCount=0 obj=0x41734d80 self=0x40054480
  | sysTid=9438 nice=-6 sched=0/0 cgrp=apps handle=1075466580
  | state=S schedstat=( 3675229609 491866105 6043 ) utm=250 stm=117 core=2
  at aal.b(SourceFile:~287)
  - waiting to lock <0x41dbfda8> (a java.lang.Object) held by tid=18 (AdWorker #3)
  at abm.f(SourceFile:33)
  at xq.r(SourceFile:593)
  at xq.b(SourceFile:168)
  at ya.onTransact(SourceFile:59)

  at android.os.Binder.transact(Binder.java:361)
  at com.google.android.gms.internal.ac$a$a.destroy((null):-1)
  at com.google.android.gms.ads.AdView.destroy((null):-1)

  at com.stest.test.activitys.AdActivity.onDestroy(AdActivity.java:96)
  at com.stest.test.activitys.CircleMainActivity.onDestroy(CircleMainActivity.java:181)
  at android.app.Activity.performDestroy(Activity.java:5499)
  at android.app.Instrumentation.callActivityOnDestroy(Instrumentation.java:1117)
  at android.app.ActivityThread.performDestroyActivity(ActivityThread.java:3511)
  at android.app.ActivityThread.handleDestroyActivity(ActivityThread.java:3542)
  at android.app.ActivityThread.access$1400(ActivityThread.java:145)
  at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1259)
  at android.os.Handler.dispatchMessage(Handler.java:102)
  at android.os.Looper.loop(Looper.java:136)
  at android.app.ActivityThread.main(ActivityThread.java:5088)
  at java.lang.reflect.Method.invokeNative(Native Method)
  at java.lang.reflect.Method.invoke(Method.java:515)
  at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:781)
  at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:597)
  at dalvik.system.NativeStart.main(Native Method)

"AdWorker #10" prio=5 tid=26 NATIVE
  | group="main" sCount=1 dsCount=0 obj=0x41d77658 self=0x5dd4dfb8
  | sysTid=9624 nice=10 sched=0/0 cgrp=apps/bg_non_interactive handle=1574233104
  | state=S schedstat=( 675708 6886583 3 ) utm=0 stm=0 core=3
  #00  pc 0002063c  /system/lib/libc.so (__ioctl+8)
  #01  pc 0002d087  /system/lib/libc.so (ioctl+14)
  #02  pc 0001d405  /system/lib/libbinder.so (android::IPCThreadState::talkWithDriver(bool)+140)
  #03  pc 0001d8ef  /system/lib/libbinder.so (android::IPCThreadState::waitForResponse(android::Parcel*, int*)+42)
  #04  pc 0001daf7  /system/lib/libbinder.so (android::IPCThreadState::transact(int, unsigned int, android::Parcel const&, android::Parcel*, unsigned int)+118)
  #05  pc 000197a9  /system/lib/libbinder.so (android::BpBinder::transact(unsigned int, android::Parcel const&, android::Parcel*, unsigned int)+30)
  #06  pc 00075f85  /system/lib/libandroid_runtime.so
  #07  pc 0001ea0c  /system/lib/libdvm.so (dvmPlatformInvoke+112)
  #08  pc 0004f61f  /system/lib/libdvm.so (dvmCallJNIMethod(unsigned int const*, JValue*, Method const*, Thread*)+398)
  #09  pc 00027ea0  /system/lib/libdvm.so
  #10  pc 0002f398  /system/lib/libdvm.so (dvmMterpStd(Thread*)+76)
  #11  pc 0002ca3c  /system/lib/libdvm.so (dvmInterpret(Thread*, Method const*, JValue*)+184)
  #12  pc 00061a83  /system/lib/libdvm.so (dvmCallMethodV(Thread*, Method const*, Object*, bool, JValue*, std::__va_list)+338)
  #13  pc 00061aa7  /system/lib/libdvm.so (dvmCallMethod(Thread*, Method const*, Object*, JValue*, ...)+20)
  #14  pc 00056793  /system/lib/libdvm.so
  #15  pc 0000d248  /system/lib/libc.so (__thread_entry+72)
  #16  pc 0000d3e0  /system/lib/libc.so (pthread_create+240)
  at android.os.BinderProxy.transact(Native Method)
  at abb.a(SourceFile:101)
  at aas.a(SourceFile:167)
  at aas.a(SourceFile:144)
  at abn.run(SourceFile:14)
  at abp.run(SourceFile:30)
  at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1112)
  at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:587)
  at java.lang.Thread.run(Thread.java:841)

"AdWorker #9" prio=5 tid=25 NATIVE
  | group="main" sCount=1 dsCount=0 obj=0x41d3ecd8 self=0x5f2924f0
  | sysTid=9609 nice=10 sched=0/0 cgrp=apps/bg_non_interactive handle=1596527368
  | state=S schedstat=( 688124 1651252 4 ) utm=0 stm=0 core=0
  #00  pc 0002063c  /system/lib/libc.so (__ioctl+8)
  #01  pc 0002d087  /system/lib/libc.so (ioctl+14)
  #02  pc 0001d405  /system/lib/libbinder.so (android::IPCThreadState::talkWithDriver(bool)+140)
  #03  pc 0001d8ef  /system/lib/libbinder.so (android::IPCThreadState::waitForResponse(android::Parcel*, int*)+42)
  #04  pc 0001daf7  /system/lib/libbinder.so (android::IPCThreadState::transact(int, unsigned int, android::Parcel const&, android::Parcel*, unsigned int)+118)
  #05  pc 000197a9  /system/lib/libbinder.so (android::BpBinder::transact(unsigned int, android::Parcel const&, android::Parcel*, unsigned int)+30)
  #06  pc 00075f85  /system/lib/libandroid_runtime.so
  #07  pc 0001ea0c  /system/lib/libdvm.so (dvmPlatformInvoke+112)
  #08  pc 0004f61f  /system/lib/libdvm.so (dvmCallJNIMethod(unsigned int const*, JValue*, Method const*, Thread*)+398)
  #09  pc 00027ea0  /system/lib/libdvm.so
  #10  pc 0002f398  /system/lib/libdvm.so (dvmMterpStd(Thread*)+76)
  #11  pc 0002ca3c  /system/lib/libdvm.so (dvmInterpret(Thread*, Method const*, JValue*)+184)
  #12  pc 00061a83  /system/lib/libdvm.so (dvmCallMethodV(Thread*, Method const*, Object*, bool, JValue*, std::__va_list)+338)
  #13  pc 00061aa7  /system/lib/libdvm.so (dvmCallMethod(Thread*, Method const*, Object*, JValue*, ...)+20)
  #14  pc 00056793  /system/lib/libdvm.so
  #15  pc 0000d248  /system/lib/libc.so (__thread_entry+72)
  #16  pc 0000d3e0  /system/lib/libc.so (pthread_create+240)
  at android.os.BinderProxy.transact(Native Method)
  at abb.a(SourceFile:101)
  at aas.a(SourceFile:167)
  at aas.a(SourceFile:144)
  at abn.run(SourceFile:14)
  at abp.run(SourceFile:30)
  at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1112)
  at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:587)
  at java.lang.Thread.run(Thread.java:841)

"AdWorker #8" prio=5 tid=24 NATIVE
  | group="main" sCount=1 dsCount=0 obj=0x41d05ce0 self=0x5f253a48
  | sysTid=9589 nice=10 sched=0/0 cgrp=apps/bg_non_interactive handle=1596331424
  | state=S schedstat=( 650250 427376 2 ) utm=0 stm=0 core=0
  #00  pc 0002063c  /system/lib/libc.so (__ioctl+8)
  #01  pc 0002d087  /system/lib/libc.so (ioctl+14)
  #02  pc 0001d405  /system/lib/libbinder.so (android::IPCThreadState::talkWithDriver(bool)+140)
  #03  pc 0001d8ef  /system/lib/libbinder.so (android::IPCThreadState::waitForResponse(android::Parcel*, int*)+42)
  #04  pc 0001daf7  /system/lib/libbinder.so (android::IPCThreadState::transact(int, unsigned int, android::Parcel const&, android::Parcel*, unsigned int)+118)
  #05  pc 000197a9  /system/lib/libbinder.so (android::BpBinder::transact(unsigned int, android::Parcel const&, android::Parcel*, unsigned int)+30)
  #06  pc 00075f85  /system/lib/libandroid_runtime.so
  #07  pc 0001ea0c  /system/lib/libdvm.so (dvmPlatformInvoke+112)
  #08  pc 0004f61f  /system/lib/libdvm.so (dvmCallJNIMethod(unsigned int const*, JValue*, Method const*, Thread*)+398)
  #09  pc 00027ea0  /system/lib/libdvm.so
  #10  pc 0002f398  /system/lib/libdvm.so (dvmMterpStd(Thread*)+76)
  #11  pc 0002ca3c  /system/lib/libdvm.so (dvmInterpret(Thread*, Method const*, JValue*)+184)
  #12  pc 00061a83  /system/lib/libdvm.so (dvmCallMethodV(Thread*, Method const*, Object*, bool, JValue*, std::__va_list)+338)
  #13  pc 00061aa7  /system/lib/libdvm.so (dvmCallMethod(Thread*, Method const*, Object*, JValue*, ...)+20)
  #14  pc 00056793  /system/lib/libdvm.so
  #15  pc 0000d248  /system/lib/libc.so (__thread_entry+72)
  #16  pc 0000d3e0  /system/lib/libc.so (pthread_create+240)
  at android.os.BinderProxy.transact(Native Method)
  at abb.a(SourceFile:101)
  at aas.a(SourceFile:167)
  at aas.a(SourceFile:144)
  at abn.run(SourceFile:14)
  at abp.run(SourceFile:30)
  at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1112)
  at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:587)
  at java.lang.Thread.run(Thread.java:841)

"AdWorker #7" prio=5 tid=23 NATIVE
  | group="main" sCount=1 dsCount=0 obj=0x41ccd2e8 self=0x5f1e8fc0
  | sysTid=9571 nice=10 sched=0/0 cgrp=apps/bg_non_interactive handle=1595839512
  | state=S schedstat=( 651500 504209 1 ) utm=0 stm=0 core=0
  #00  pc 0002063c  /system/lib/libc.so (__ioctl+8)
  #01  pc 0002d087  /system/lib/libc.so (ioctl+14)
  #02  pc 0001d405  /system/lib/libbinder.so (android::IPCThreadState::talkWithDriver(bool)+140)
  #03  pc 0001d8ef  /system/lib/libbinder.so (android::IPCThreadState::waitForResponse(android::Parcel*, int*)+42)
  #04  pc 0001daf7  /system/lib/libbinder.so (android::IPCThreadState::transact(int, unsigned int, android::Parcel const&, android::Parcel*, unsigned int)+118)
  #05  pc 000197a9  /system/lib/libbinder.so (android::BpBinder::transact(unsigned int, android::Parcel const&, android::Parcel*, unsigned int)+30)
  #06  pc 00075f85  /system/lib/libandroid_runtime.so
  #07  pc 0001ea0c  /system/lib/libdvm.so (dvmPlatformInvoke+112)
  #08  pc 0004f61f  /system/lib/libdvm.so (dvmCallJNIMethod(unsigned int const*, JValue*, Method const*, Thread*)+398)
  #09  pc 00027ea0  /system/lib/libdvm.so
  #10  pc 0002f398  /system/lib/libdvm.so (dvmMterpStd(Thread*)+76)
  #11  pc 0002ca3c  /system/lib/libdvm.so (dvmInterpret(Thread*, Method const*, JValue*)+184)
  #12  pc 00061a83  /system/lib/libdvm.so (dvmCallMethodV(Thread*, Method const*, Object*, bool, JValue*, std::__va_list)+338)
  #13  pc 00061aa7  /system/lib/libdvm.so (dvmCallMethod(Thread*, Method const*, Object*, JValue*, ...)+20)
  #14  pc 00056793  /system/lib/libdvm.so
  #15  pc 0000d248  /system/lib/libc.so (__thread_entry+72)
  #16  pc 0000d3e0  /system/lib/libc.so (pthread_create+240)
  at android.os.BinderProxy.transact(Native Method)
  at abb.a(SourceFile:101)
  at aas.a(SourceFile:167)
  at aas.a(SourceFile:144)
  at abn.run(SourceFile:14)
  at abp.run(SourceFile:30)
  at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1112)
  at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:587)
  at java.lang.Thread.run(Thread.java:841)

"AdWorker #6" prio=5 tid=22 NATIVE
  | group="main" sCount=1 dsCount=0 obj=0x41c43b20 self=0x5d9cc5a0
  | sysTid=9497 nice=10 sched=0/0 cgrp=apps/bg_non_interactive handle=1570556408
  | state=S schedstat=( 1334166 2262333 4 ) utm=0 stm=0 core=1
  #00  pc 0002063c  /system/lib/libc.so (__ioctl+8)
  #01  pc 0002d087  /system/lib/libc.so (ioctl+14)
  #02  pc 0001d405  /system/lib/libbinder.so (android::IPCThreadState::talkWithDriver(bool)+140)
  #03  pc 0001d8ef  /system/lib/libbinder.so (android::IPCThreadState::waitForResponse(android::Parcel*, int*)+42)
  #04  pc 0001daf7  /system/lib/libbinder.so (android::IPCThreadState::transact(int, unsigned int, android::Parcel const&, android::Parcel*, unsigned int)+118)
  #05  pc 000197a9  /system/lib/libbinder.so (android::BpBinder::transact(unsigned int, android::Parcel const&, android::Parcel*, unsigned int)+30)
  #06  pc 00075f85  /system/lib/libandroid_runtime.so
  #07  pc 0001ea0c  /system/lib/libdvm.so (dvmPlatformInvoke+112)
  #08  pc 0004f61f  /system/lib/libdvm.so (dvmCallJNIMethod(unsigned int const*, JValue*, Method const*, Thread*)+398)
  #09  pc 00027ea0  /system/lib/libdvm.so
  #10  pc 0002f398  /system/lib/libdvm.so (dvmMterpStd(Thread*)+76)
  #11  pc 0002ca3c  /system/lib/libdvm.so (dvmInterpret(Thread*, Method const*, JValue*)+184)
  #12  pc 00061a83  /system/lib/libdvm.so (dvmCallMethodV(Thread*, Method const*, Object*, bool, JValue*, std::__va_list)+338)
  #13  pc 00061aa7  /system/lib/libdvm.so (dvmCallMethod(Thread*, Method const*, Object*, JValue*, ...)+20)
  #14  pc 00056793  /system/lib/libdvm.so
  #15  pc 0000d248  /system/lib/libc.so (__thread_entry+72)
  #16  pc 0000d3e0  /system/lib/libc.so (pthread_create+240)
  at android.os.BinderProxy.transact(Native Method)
  at abb.a(SourceFile:101)
  at aas.a(SourceFile:167)
  at aas.a(SourceFile:144)
  at abn.run(SourceFile:14)
  at abp.run(SourceFile:30)
  at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1112)
  at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:587)
  at java.lang.Thread.run(Thread.java:841)

"AdWorker #5" prio=5 tid=21 WAIT
  | group="main" sCount=1 dsCount=0 obj=0x41c30868 self=0x5d786650
  | sysTid=9490 nice=10 sched=0/0 cgrp=apps/bg_non_interactive handle=1546781256
  | state=S schedstat=( 117882092 131898916 336 ) utm=8 stm=3 core=2
  at java.lang.Object.wait(Native Method)
  - waiting on <0x41c309d0> (a java.lang.VMThread) held by tid=21 (AdWorker #5)
  at java.lang.Thread.parkFor(Thread.java:1205)
  at sun.misc.Unsafe.park(Unsafe.java:325)
  at java.util.concurrent.locks.LockSupport.park(LockSupport.java:157)
  at java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:2017)
  at java.util.concurrent.LinkedBlockingQueue.take(LinkedBlockingQueue.java:410)
  at asj.a(SourceFile:53)
  at xh.a(SourceFile:124)
  at rz.d(SourceFile:88)
  at rz.b(SourceFile:129)
  at rw.a(SourceFile:239)
  at rw.a(SourceFile:176)
  at aal.a(SourceFile:116)
  at abn.run(SourceFile:14)
  at abp.run(SourceFile:30)
  at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1112)
  at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:587)
  at java.lang.Thread.run(Thread.java:841)

"Binder_3" prio=5 tid=20 NATIVE
  | group="main" sCount=1 dsCount=0 obj=0x41c17248 self=0x5c326ab0
  | sysTid=9485 nice=0 sched=0/0 cgrp=apps handle=1546809656
  | state=S schedstat=( 57466167 29965795 413 ) utm=2 stm=3 core=0
  #00  pc 0002063c  /system/lib/libc.so (__ioctl+8)
  #01  pc 0002d087  /system/lib/libc.so (ioctl+14)
  #02  pc 0001d405  /system/lib/libbinder.so (android::IPCThreadState::talkWithDriver(bool)+140)
  #03  pc 0001db0f  /system/lib/libbinder.so (android::IPCThreadState::getAndExecuteCommand()+6)
  #04  pc 0001dba5  /system/lib/libbinder.so (android::IPCThreadState::joinThreadPool(bool)+48)
  #05  pc 000219cd  /system/lib/libbinder.so
  #06  pc 0000ecc1  /system/lib/libutils.so (android::Thread::_threadLoop(void*)+216)
  #07  pc 000518e1  /system/lib/libandroid_runtime.so (android::AndroidRuntime::javaThreadShell(void*)+68)
  #08  pc 0000e7f3  /system/lib/libutils.so
  #09  pc 0000d248  /system/lib/libc.so (__thread_entry+72)
  #10  pc 0000d3e0  /system/lib/libc.so (pthread_create+240)
  at dalvik.system.NativeStart.run(Native Method)

"AdWorker #4" prio=5 tid=19 NATIVE
  | group="main" sCount=1 dsCount=0 obj=0x41c165a8 self=0x5db08c78
  | sysTid=9483 nice=10 sched=0/0 cgrp=apps/bg_non_interactive handle=1571852496
  | state=S schedstat=( 621583 485917 3 ) utm=0 stm=0 core=3
  #00  pc 0002063c  /system/lib/libc.so (__ioctl+8)
  #01  pc 0002d087  /system/lib/libc.so (ioctl+14)
  #02  pc 0001d405  /system/lib/libbinder.so (android::IPCThreadState::talkWithDriver(bool)+140)
  #03  pc 0001d8ef  /system/lib/libbinder.so (android::IPCThreadState::waitForResponse(android::Parcel*, int*)+42)
  #04  pc 0001daf7  /system/lib/libbinder.so (android::IPCThreadState::transact(int, unsigned int, android::Parcel const&, android::Parcel*, unsigned int)+118)
  #05  pc 000197a9  /system/lib/libbinder.so (android::BpBinder::transact(unsigned int, android::Parcel const&, android::Parcel*, unsigned int)+30)
  #06  pc 00075f85  /system/lib/libandroid_runtime.so
  #07  pc 0001ea0c  /system/lib/libdvm.so (dvmPlatformInvoke+112)
  #08  pc 0004f61f  /system/lib/libdvm.so (dvmCallJNIMethod(unsigned int const*, JValue*, Method const*, Thread*)+398)
  #09  pc 00027ea0  /system/lib/libdvm.so
  #10  pc 0002f398  /system/lib/libdvm.so (dvmMterpStd(Thread*)+76)
  #11  pc 0002ca3c  /system/lib/libdvm.so (dvmInterpret(Thread*, Method const*, JValue*)+184)
  #12  pc 00061a83  /system/lib/libdvm.so (dvmCallMethodV(Thread*, Method const*, Object*, bool, JValue*, std::__va_list)+338)
  #13  pc 00061aa7  /system/lib/libdvm.so (dvmCallMethod(Thread*, Method const*, Object*, JValue*, ...)+20)
  #14  pc 00056793  /system/lib/libdvm.so
  #15  pc 0000d248  /system/lib/libc.so (__thread_entry+72)
  #16  pc 0000d3e0  /system/lib/libc.so (pthread_create+240)
  at android.os.BinderProxy.transact(Native Method)
  at abb.a(SourceFile:101)
  at aas.a(SourceFile:167)
  at aas.a(SourceFile:144)
  at abn.run(SourceFile:14)
  at abp.run(SourceFile:30)
  at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1112)
  at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:587)
  at java.lang.Thread.run(Thread.java:841)

"AdWorker #3" prio=5 tid=18 WAIT
  | group="main" sCount=1 dsCount=0 obj=0x41c024f8 self=0x5d910a80
  | sysTid=9482 nice=10 sched=0/0 cgrp=apps/bg_non_interactive handle=1569787608
  | state=S schedstat=( 16531874 18794877 86 ) utm=1 stm=0 core=3
  at java.lang.Object.wait(Native Method)
  - waiting on <0x41c02628> (a java.lang.VMThread) held by tid=18 (AdWorker #3)
  at java.lang.Thread.parkFor(Thread.java:1205)
  at sun.misc.Unsafe.park(Unsafe.java:325)
  at java.util.concurrent.locks.LockSupport.park(LockSupport.java:157)
  at java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:2017)
  at java.util.concurrent.LinkedBlockingQueue.take(LinkedBlockingQueue.java:410)
  at asj.a(SourceFile:53)
  at xh.a(SourceFile:124)
  at rz.d(SourceFile:88)
  at rz.b(SourceFile:129)
  at rw.a(SourceFile:239)
  at rw.a(SourceFile:176)
  at aal.a(SourceFile:116)
  at abn.run(SourceFile:14)
  at abp.run(SourceFile:30)
  at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1112)
  at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:587)
  at java.lang.Thread.run(Thread.java:841)

"AdWorker #2" prio=5 tid=17 NATIVE
  | group="main" sCount=1 dsCount=0 obj=0x41be4098 self=0x5d844010
  | sysTid=9475 nice=10 sched=0/0 cgrp=apps/bg_non_interactive handle=1568949352
  | state=S schedstat=( 1377502 4963791 13 ) utm=0 stm=0 core=0
  #00  pc 0002063c  /system/lib/libc.so (__ioctl+8)
  #01  pc 0002d087  /system/lib/libc.so (ioctl+14)
  #02  pc 0001d405  /system/lib/libbinder.so (android::IPCThreadState::talkWithDriver(bool)+140)
  #03  pc 0001d8ef  /system/lib/libbinder.so (android::IPCThreadState::waitForResponse(android::Parcel*, int*)+42)
  #04  pc 0001daf7  /system/lib/libbinder.so (android::IPCThreadState::transact(int, unsigned int, android::Parcel const&, android::Parcel*, unsigned int)+118)
  #05  pc 000197a9  /system/lib/libbinder.so (android::BpBinder::transact(unsigned int, android::Parcel const&, android::Parcel*, unsigned int)+30)
  #06  pc 00075f85  /system/lib/libandroid_runtime.so
  #07  pc 0001ea0c  /system/lib/libdvm.so (dvmPlatformInvoke+112)
  #08  pc 0004f61f  /system/lib/libdvm.so (dvmCallJNIMethod(unsigned int const*, JValue*, Method const*, Thread*)+398)
  #09  pc 00027ea0  /system/lib/libdvm.so
  #10  pc 0002f398  /system/lib/libdvm.so (dvmMterpStd(Thread*)+76)
  #11  pc 0002ca3c  /system/lib/libdvm.so (dvmInterpret(Thread*, Method const*, JValue*)+184)
  #12  pc 00061a83  /system/lib/libdvm.so (dvmCallMethodV(Thread*, Method const*, Object*, bool, JValue*, std::__va_list)+338)
  #13  pc 00061aa7  /system/lib/libdvm.so (dvmCallMethod(Thread*, Method const*, Object*, JValue*, ...)+20)
  #14  pc 00056793  /system/lib/libdvm.so
  #15  pc 0000d248  /system/lib/libc.so (__thread_entry+72)
  #16  pc 0000d3e0  /system/lib/libc.so (pthread_create+240)
  at android.os.BinderProxy.transact(Native Method)
  at abb.a(SourceFile:101)
  at aas.a(SourceFile:167)
  at aas.a(SourceFile:144)
  at abn.run(SourceFile:14)
  at abp.run(SourceFile:30)
  at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1112)
  at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:587)
  at java.lang.Thread.run(Thread.java:841)

"AdWorker #1" prio=5 tid=16 TIMED_WAIT
  | group="main" sCount=1 dsCount=0 obj=0x41bbf458 self=0x5c2c9e68
  | sysTid=9474 nice=10 sched=0/0 cgrp=apps/bg_non_interactive handle=1546429120
  | state=S schedstat=( 23610332 16863542 72 ) utm=2 stm=0 core=1
  at java.lang.Object.wait(Native Method)
  - waiting on <0x41bbe250> (a java.lang.Object)
  at java.lang.Object.wait(Object.java:401)
  at aal.b(SourceFile:455)
  at aal.a(SourceFile:138)
  at abn.run(SourceFile:14)
  at abp.run(SourceFile:30)
  at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1112)
  at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:587)
  at java.lang.Thread.run(Thread.java:841)

"CleanupReference" daemon prio=5 tid=15 WAIT
  | group="main" sCount=1 dsCount=0 obj=0x41bb5880 self=0x5c2c5318
  | sysTid=9473 nice=0 sched=0/0 cgrp=apps handle=1546409840
  | state=S schedstat=( 280750 2376751 3 ) utm=0 stm=0 core=1
  at java.lang.Object.wait(Native Method)
  - waiting on <0x41bb57b8> (a java.lang.ref.ReferenceQueue)
  at java.lang.Object.wait(Object.java:401)
  at java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:102)
  at java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:73)
  at com.android.org.chromium.content.common.CleanupReference$1.run(CleanupReference.java:48)

 

[Andrej van der Zee]

I am having this issue too after upgrading to AdMob in GMS. We are receiving a lot of complaints and bad reviews for a month now. In the meanwhile, is there a workaround except for not calling AdView.onDestroy()? 

Thanks,
Andrej

On Monday, November 25, 2013 8:30:24 PM UTC+1, Gert wrote:

[Martin van Z]

Same issue here. I Added the destroy to fix the illegalargument error and now getting ANR's

Device:

Droid MAXX

(a java.lang.Object) held by tid=20 (AdWorker #7)

at abm.f(SourceFile:33)
at xq.r(SourceFile:593)
at xq.b(SourceFile:168)
at ya.onTransact(SourceFile:59)
at android.os.Binder.transact(Binder.java:361)

at com.google.android.gms.internal.g.b((null):-1)
at com.google.android.gms.internal.p.a((null):-1)
at com.google.android.gms.ads.f.a((null):-1)
at com.cubeactive.qnotelistfree.ay.onDestroy(SourceFile:345)
at com.cubeactive.qnotelistfree.NotelistActivity.onDestroy(SourceFile:200)
at android.app.Activity.performDestroy(Activity.java:5432)
at android.app.Instrumentation.callActivityOnDestroy(Instrumentation.java:1140)
at android.app.ActivityThread.performDestroyActivity(ActivityThread.java:3546)
at android.app.ActivityThread.handleDestroyActivity(ActivityThread.java:3577)
at android.app.ActivityThread.handleRelaunchActivity(ActivityThread.java:3777)
at android.app.ActivityThread.access$800(ActivityThread.java:139)
at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1417)
at android.os.Handler.dispatchMessage(Handler.java:102)
at android.os.Looper.loop(Looper.java:137)
at android.app.ActivityThread.main(ActivityThread.java:5083)
at java.lang.reflect.Method.invokeNative(Native Method)
at java.lang.reflect.Method.invoke(Method.java:515)
at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:777)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:593)
at dalvik.system.NativeStart.main(Native Method)

On Monday, November 25, 2013 8:30:24 PM UTC+1, Gert wrote:

[gillis haasnoot]

Same issue here.

I get 

java.lang.IllegalArgumentException: Service not registered: asj@406aa430
at android.app.LoadedApk.forgetServiceDispatcher(LoadedApk.java:891)

when i dont implement AdView.destroy.

But when i implement it my apps are getting anr. To reproduce it, just create a simple hello world app with admob somewhere visible.

Also implement a broadcast receiver which opens a new instance of the app. NEW_TASK.

Open the app.  

Then trigger the broadcast receiver from for example a push notification. A new instance will be opened. Press back button to close the app. You will end up in the initial instance. 

Press home screen and then reopen the app. Your app now has an ANR.

Op donderdag 30 januari 2014 10:52:07 UTC+1 schreef Martin van Z:

[Eric Leichtenschlag]

What version of Google Play services is installed on the device? Version 4.2 is rolling out this week. Does it still happen on 4.2?

Thanks,

Eric

[dm1973]

I have had a couple crash also (2 yesterday). Is there any way to tell from a google marketplace crash report what version of GPS is installed?

[gillis haasnoot]

i am running revision 14

Op zaterdag 8 februari 2014 00:30:15 UTC+1 schreef Eric Leichtenschlag:

[Eric Leichtenschlag]

There isn't a way right now to see what version of the service is running from the stack trace. 4.2 (will be revision 15) rolls out more broadly this week.

Gillis, can you attach the sample app you're using with the Broadcast receiver?

Thanks,
Eric

[gillis haasnoot]

It sounds silly, but i have a had time reproducing it.

I am slowely building from scratch an application with its structure identical to the one giving problems.

One thing i can say for sure is that a simple mainactivity with one inflated layout with inside an ad doesnt give problems.

It has maybe something to do with combination of fragments and maybe even thirdparty viewpage indicators/ sherlock actionbar.

When i have some more info to share i will post it here.

Op maandag 10 februari 2014 19:27:00 UTC+1 schreef Eric Leichtenschlag:

[Hunter Peress]

I have a crash too: http://stackoverflow.com/questions/21841171/intellij-idea-the-google-play-services-resources-were-not-found

And I have installed r15 of play services via the SDK in android studio

But Do I need to also upgrade the version string in build.gradle from:

compile 'com.google.android.gms:play-services:4.0.30'

to perhaps 
compile 'com.google.android.gms:play-services:4.2' ????

[Bjørn Christian Seime]

The 4.2 update seems to have solved the issue. I have not received any ANR reports at all after migrating to 4.2.

[Eric Leichtenschlag]

That's great news - thanks for the feedback!

[Eric Leichtenschlag]

Yeah that sounds like changing that dependency will have you compiling 4.2 as part of your app. But the trace from stackoverflow looks to already be running 4.2 because that's what the service had.

Are you calling adView.destroy() in your app?

Thanks,

Eric

[Bjørn Christian Seime]

Btw, I am still receiving several reports on "IllegalArgumentException: Service not registered". I am calling destroy() on AdView as described in documentation.

java.lang.IllegalArgumentException: Service not registered: azc@42399488

at android.app.LoadedApk.forgetServiceDispatcher(LoadedApk.java:926)

at android.app.ContextImpl.unbindService(ContextImpl.java:1795)

at android.content.ContextWrapper.unbindService(ContextWrapper.java:491)

at wr.a(SourceFile:135)

at tt.d(SourceFile:88)

at tt.b(SourceFile:129)

at tq.a(SourceFile:239)

at tq.a(SourceFile:176)

at zv.a(SourceFile:117)

at aay.run(SourceFile:14)

at aba.run(SourceFile:30)

at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1080)

at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:573)

at java.lang.Thread.run(Thread.java:856)

[Fede Fdez]

Same here, I'm calling pause, destroy, and resume (version 4.2.42). I'm receiving similar reports:

AdWorker #2 java.lang.IllegalArgumentException: Service not registered: azc@411cbc10
android.app.LoadedApk.forgetServiceDispatcher(LoadedApk.java:888)
android.app.ContextImpl.unbindService(ContextImpl.java:1170)
android.content.ContextWrapper.unbindService(ContextWrapper.java:375)
wr.a(SourceFile:135)
tt.d(SourceFile:88)
tt.b(SourceFile:129)
tq.a(SourceFile:239)
tq.a(SourceFile:176)
zv.a(SourceFile:117)
aay.run(SourceFile:14)
aba.run(SourceFile:30)
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1076) java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:569)
java.lang.Thread.run(Thread.java:856)

There is a workaround for this?

[Eric Leichtenschlag]

Thanks for confirming this happens even if destroy is called. This is being investigated, but unfortunately there is no known workaround yet.

[Bjørn Christian Seime]

Feel free to contact me per email if you need any more details (code, crash reports, etc).

[yan MESS]

Hi everyone, I get the same issue here with the latest SDK 4.2.42, Everything in code seems good, with adview.destroy() called at OnDestroy, I tried to reproduce it but without success:

Android 4.2	1	50,0 %
Android 4.0.3 - 4.0.4	1	50,0 %

Galaxy Grand duos (baffin)	1	50,0 %
Xperia miro (ST23i)	1	50,0 %

java.lang.IllegalArgumentException: Service not registered: azc@415b9f98
at android.app.LoadedApk.forgetServiceDispatcher(LoadedApk.java:888)
at android.app.ContextImpl.unbindService(ContextImpl.java:1170)
at android.content.ContextWrapper.unbindService(ContextWrapper.java:375)

at wr.a(SourceFile:135)
at tt.d(SourceFile:88)
at tt.b(SourceFile:129)
at tq.a(SourceFile:239)
at tq.a(SourceFile:176)
at zv.a(SourceFile:117)
at aay.run(SourceFile:14)
at aba.run(SourceFile:30)

at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1076)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:569)
at java.lang.Thread.run(Thread.java:856)

[yan MESS]

Another bug report suspected to be from GPS  Ads:

Droid 4 (cdma_maserati)	2	66,7 %
hwG525-U00	1	33,3 %

java.lang.NullPointerException
at android.os.Parcel.readException(Parcel.java:1431)
at android.os.Parcel.readException(Parcel.java:1379)
at aal.a(SourceFile:102)
at aac.a(SourceFile:167)
at aac.a(SourceFile:144)

at aay.run(SourceFile:14)
at aba.run(SourceFile:30)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1076)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:569)
at java.lang.Thread.run(Thread.java:856)

-

[Hunter Peress]

Hi Eric,

Due to this issue, I will be removing admob from my app today. I will assume that this thread is the place where the resolution of this issue will be announced, unless you can inform me of another location where I should stay posted for updates.

[Ian Dixon]

I'm in the same boat as Hunter. I'm heavily integrated with Admob in all my apps, but I cannot continue to tolerate a library that causes my apps to crash without a meaningful timeframe as to when a fix will be ready. I'm not seeing the urgency from Admob that I would expect on this issue, and so I am preparing to migrate to another ad provider.

[Eric Leichtenschlag]

Thanks for the update. I've made sure to let the team know we're losing pubs due to the extent of this bug. Unfortunately I still don't have a time-frame for a fix.

I will update this thread when a fix is available.

[Bjørn Christian Seime]

Ditto. I disabled all Admob ads as I got several thousand crash reports the last couple of days. I hope Google is quicker to fix this issue that the ANR one...

[Eric Leichtenschlag]

SDK team is having a tough time figuring out how this crash could be happening. Has anyone been able to reproduce this in a sample app, or are these reports just from Play store / 3rd party crash reporting tools? Are there particular devices where crashes have been more common?

Thanks,
Eric

[Fede Fdez]

Hi Eric,

I can't reproduce the error in a sample app, all I got are reports on Play Store and Analytics. The devices and android version are:

Android 4.0.3 - 4.0.4 9 81,8%

Android 2.3.3 - 2.3.7 1 9,1%

Android 4.1 1 9,1%

Xperia tipo (ST21i) 7 63,6%

crane-inet 1 9,1%

Xperia miro (ST23i) 1 9,1%

Optimus L5 (m4) 1 9,1%

Galaxy Ace (GT-S5830) 1 9,1%

Thanks!

[Eric Leichtenschlag]

Thanks Fede. And we had 1 report in this other thread with a more information in the crash report:

01-24 00:16:26.745    1458-1458/com.inmobi.tmi.ui E/ActivityThread﹕ Activity com.inmobi.tmi.ui.MainActivity has leaked ServiceConnection asj@416f7e18 that was originally bound here

    android.app.ServiceConnectionLeaked: Activity com.inmobi.tmi.ui.MainActivity has leaked ServiceConnection asj@416f7e18 that was originally bound here

            at android.app.LoadedApk$ServiceDispatcher.<init>(LoadedApk.java:969)

            at android.app.LoadedApk.getServiceDispatcher(LoadedApk.java:863)

            at android.app.ContextImpl.bindService(ContextImpl.java:1418)

            at android.app.ContextImpl.bindService(ContextImpl.java:1407)

            at android.content.ContextWrapper.bindService(ContextWrapper.java:473)

            at xh.b(SourceFile:92)

            at xh.a(SourceFile:121)

            at rz.d(SourceFile:88)

            at rz.b(SourceFile:129)

            at rw.a(SourceFile:239)

            at rw.a(SourceFile:176)

            at aal.a(SourceFile:116)

            at abn.run(SourceFile:14)

            at abp.run(SourceFile:30)

            at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1080)

            at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:573)

            at java.lang.Thread.run(Thread.java:856)

01-24 00:16:26.745    1458-1478/com.inmobi.tmi.ui E/AndroidRuntime﹕ FATAL EXCEPTION: AdWorker #1

    java.lang.IllegalArgumentException: Service not registered: asj@416f7e18

            at android.app.LoadedApk.forgetServiceDispatcher(LoadedApk.java:921)

            at android.app.ContextImpl.unbindService(ContextImpl.java:1451)

            at android.content.ContextWrapper.unbindService(ContextWrapper.java:484)

            at xh.a(SourceFile:135)

            at rz.d(SourceFile:88)

            at rz.b(SourceFile:129)

            at rw.a(SourceFile:239)

            at rw.a(SourceFile:176)

            at aal.a(SourceFile:116)

            at abn.run(SourceFile:14)

            at abp.run(SourceFile:30)

            at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1080)

            at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:573)

            at java.lang.Thread.run(Thread.java:856)

Everyone on this thread is just reporting the service not registered. Do you guys also have the same/similar first trace?

[Eric Leichtenschlag]

Hunter/Ian/Bjørn,

Can you also provide your OS and device distribution from this crash from the Play store. Is it consistent with Fede's reportings of Xperia Tipo on Android 4.0.3 - 4.0.4?

[Ian Dixon]

Eric,

I was seeing this on a Motorola G running 4.4.x

[Bjørn Christian Seime]

I am getting this crash report for all kind of devices, from 2.3.5 up to 4.4.2. This is information is based on bug reports from Acralyzer. Just a few percent of the user base actually submit reports through the default reporting system, so the numbers on Developer dashboard does not provide any useful statistics.

[Hunter Peress]

I have no new information to provide. I see the same results as Ian/Bjørn 

Also, I am no longer running admob and I am wasting time and energy searching for a new ad provider, so my ability to provide useful feedback data is rapidly diminishing. 

However, the first step is to actually reproduce the bug. 

Does anyone see what steps to take to reproduce the bug? 

[yan MESS]

Android 4.1	3	37,5 %
Android 4.2	2	25,0 %
Android 4.0.3 - 4.0.4	2	25,0 %

Android 2.3.3 - 2.3.7

1

12,5 %

Galaxy Grand duos (baffin)	2	25,0 %
Galaxy Trend Lite (kylevess)	1	12,5 %
Xperia miro (ST23i)	1	12,5 %
Galaxy Win (delos3geur)	1	12,5 %
HTC One S (villec2)	1	12,5 %
Galaxy S4 (jfltecan)	1	12,5 %
Galaxy S2 (GT-I9100)	1	12,5 %

Xperia miro (ST23i) seems to be a good candidate for testing as i see it on Fede's report too.

What's strange about this bug is that it occurs even when catching throwable in all Adview calls.

Le lundi 25 novembre 2013 20:30:24 UTC+1, Gert a écrit :

<span style="font-family: monospace; line-height: 18px; text-indent: -26px; background-color: rgb(245, 245, 2

...

[Chris Smith]

The devices I'm seeing this error on:

- GT-I9100
- DROID3
- Galaxy Nexus
- SPH-M840
- SCH-S738C
- Desire HD
- SGH-T989

...

[Kevin Liu]

I'm seeing service not registered in my stacktraces and serviceconnection leaked in my logcats. I have not been able to reproduce the issue on my HTC One 4.4 but I've been getting a lot of those in my error reporter (across many devices and versions)

</d

...

[Eric Leichtenschlag]

Thanks guys. We've identified the source of the crash and it will be fixed in the next release.

<di

...

[Kevin Liu]

Thanks Eric. That's good to know. Is there an ETA for the next release? I'm trying to decide whether I should remove admob and update the app or just ride out the storm of crashes and bad reviews. 

On Monday, March 10, 2014 5:12:22 PM UTC-4, Eric Leichtenschlag wrote:

Thanks guys. We've identified the source of the crash and it will be fixed in the next release.

On Monday, March 10, 2014 5:41:03 AM UTC-7, Kevin Liu wrote:

I'm seeing service not registered in my stacktraces and serviceconnection leaked in my logcats. I have not been able to reproduce the issue on my HTC One 4.4 but I've been getting a lot of those in my error reporter (across many devices and versions)

On Tuesday, March 4, 2014 10:57:45 AM UTC-5, Eric Leichtenschlag wrote:

Thanks Fede. And we had 1 report in this other thread with a more information in the crash report:

01-24 00:16:26.745    1458-1458/com.inmobi.tmi.ui E/ActivityThread﹕ Activity com.inmobi.tmi.ui.MainActivity has leaked ServiceConnection asj@416f7e18 that was originally bound here

    android.app.ServiceConnectionLeaked: Activity com.inmobi.tmi.ui.MainActivity has leaked ServiceConnection asj@416f7e18 that was originally bound here

            at android.app.LoadedApk$ServiceDispatcher.<init>(LoadedApk.java:969)

            at android.app.LoadedApk.getServiceDispatcher(LoadedApk.java:863)

            at android.app.ContextImpl.bindService(ContextImpl.java:1418)

            at android.app.ContextImpl.bindService(ContextImpl.java:1407)

            at android.content.ContextWrapper.bindService(ContextWrapper.java:473)

            at xh.b(SourceFile:92)

            at xh.a(SourceFile:121)

            at rz.d(SourceFile:88)

            at rz.b(SourceFile:129)

            at rw.a(SourceFile:239)

            at rw.a(SourceFile:176)

            at aal.a(SourceFile:116)

            at abn.run(SourceFile:14)

            at abp.run(SourceFile:30)

            at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1080)

            at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecuto

...

[Eric Leichtenschlag]

The next release should start rolling out sometime next week. You may also consider putting AdMob later in your mediation flow to reduce crashes, which wouldn't require a re-release if you're mediating.

On Monday, March 10, 2014 3:00:43 PM UTC-7, Kevin Liu wrote:

Thanks Eric. That's good to know. Is there an ETA for the next release? I'm trying to decide whether I should remove admob and update the app or just ride out the storm of crashes and bad reviews. 

On Monday, March 10, 2014 5:12:22 PM UTC-4, Eric Leichtenschlag wrote:

Thanks guys. We've identified the source of the crash and it will be fixed in the next release.

On Monday, March 10, 2014 5:41:03 AM UTC-7, Kevin Liu wrote:

I'm seeing service not registered in my stacktraces and serviceconnection leaked in my logcats. I have not been able to reproduce the issue on my HTC One 4.4 but I've been getting a lot of those in my error reporter (across many devices and versions)

On Tuesday, March 4, 2014 10:57:45 AM UTC-5, Eric Leichtenschlag wrote:

Thanks Fede. And we had 1 report in this other thread with a more information in the crash report:

01-24 00:16:26.745    1458-1458/com.inmobi.tmi.ui E/ActivityThread﹕ Activity com.inmobi.tmi.ui.MainActivity has leaked ServiceConnection asj@416f7e18 that was originally bound here

    android.app.ServiceConnectionLeaked: Activity com.inmobi.tmi.ui.MainActivity has leaked ServiceConnection asj@416f7e18 that was originally bound here

            at android.app.LoadedApk$ServiceDispatcher.<init>(LoadedApk.java:969)

            at android.app.LoadedApk.getServiceDispatcher(LoadedApk.java:863)

            at android.app.ContextImpl.bindService(ContextImpl.java:1418)

            at android.app.ContextImpl.bindService(ContextImpl.java:1407)

            at android.content.ContextWrapper.bindService(ContextWrapper.java:473)

            at xh.b(SourceFile:9

...

[Adrian Sulumberchean]

I was able to reproduce it on my Galaxy S (Android 2.3.7) just by switching device orientation fast (before the screen completely finishes loading). I should mention that for me is not an ANR but an actual crash and the stack trace is the same as the first one from yan:

java.lang.IllegalArgumentException: Service not registered: azc@41080558
at android.app.LoadedApk.forgetServiceDispatcher(LoadedApk.java:945)
at android.app.ContextImpl.unbindService(ContextImpl.java:1403)
at android.content.ContextWrapper.unbindService(ContextWrapper.java:375)

at wr.a(SourceFile:135)
at tt.d(SourceFile:88)
at tt.b(SourceFile:129)
at tq.a(SourceFile:239)
at tq.a(SourceFile:176)
at zv.a(SourceFile:117)
at aay.run(SourceFile:14)
at aba.run(SourceFile:30)

at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1076)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:569)

at java.lang.Thread.run(Thread.java:864)

Galaxy S (SGH-I897)	2	66.7%
ADR6425LVW (vigor)	1	33.3%

Android 2.3.3 - 2.3.7	2	66.7%

Android 4.0.3 - 4.0.4

1

33.3%

--

---
You received this message because you are subscribed to a topic in the Google Groups "Google AdMob Ads Developers" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/google-admob-ads-sdk/sePctoDJbRg/unsubscribe.
To unsubscribe from this group and all its topics, send an email to google-admob-ads...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[smrtp...@gmail.com]

Similar issue.

Galaxy Tab2 10.1, Android 4.0.3

--- pid 3648 at 2014-03-08 11:03:37 -----
Cmd line: com.smrtprjcts.edenred

DALVIK THREADS:
(mutexes: tll=0 tsl=0 tscl=0 ghl=0)
"main" prio=5 tid=1 VMWAIT
| group="main" sCount=1 dsCount=0 obj=0x40bed460 self=0x1d2add8
| sysTid=3648 nice=0 sched=0/0 cgrp=default handle=1074717864
| schedstat=( 245361325 138183600 208 ) utm=17 stm=6 core=1
at dalvik.system.DexFile.openDexFile(Native Method)
at dalvik.system.DexFile.<init>(DexFile.java:93)
at dalvik.system.DexFile.loadDex(DexFile.java:133)
at dalvik.system.DexPathList.loadDexFile(DexPathList.java:261)
at dalvik.system.DexPathList.makeDexElements(DexPathList.java:229)
at dalvik.system.DexPathList.<init>(DexPathList.java:96)
at dalvik.system.BaseDexClassLoader.<init>(BaseDexClassLoader.java:52)
at dalvik.system.DexClassLoader.<init>(DexClassLoader.java:57)
at tr.a(SourceFile:87)
at tt.a(SourceFile:68)
at xb.<init>(SourceFile:95)
at xa.<init>(SourceFile:150)
at com.google.android.gms.ads.AdManagerCreatorImpl.newAdManager(SourceFile:34)
at xm.onTransact(SourceFile:66)
at android.os.Binder.transact(Binder.java:297)
at yx.a((null):-1)
at com.google.android.gms.internal.u.b((null):-1)
at com.google.android.gms.internal.u.a((null):-1)
at com.google.android.gms.internal.ag.b((null):-1)
at com.google.android.gms.internal.ag.a((null):-1)
at com.google.android.gms.ads.AdView.loadAd((null):-1)
at com.smrtprjcts.edenred.MainActivity.onCreate(SourceFile:183)
at android.app.Activity.performCreate(Activity.java:4465)
at android.app.Instrumentation.callActivityOnCreate(Instrumentation.java:1053)
at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:1934)
at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:1995)
at android.app.ActivityThread.access$600(ActivityThread.java:128)
at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1161)
at android.os.Handler.dispatchMessage(Handler.java:99)
at android.os.Looper.loop(Looper.java:137)
at android.app.ActivityThread.main(ActivityThread.java:4514)

at java.lang.reflect.Method.invokeNative(Native Method)
at java.lang.reflect.Method.invoke(Method.java:511)

at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:790)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:557)
at dalvik.system.NativeStart.main(Native Method)

2013. november 25., hétfő 20:30:24 UTC+1 időpontban Gert a következőt írta:

Hello,

I've just received an ANR report from a user. A closer look at the stack traces attached shows that the ANR occurs in an onDestroy method, that calls the destroy of an AdView.

The project is obfuscated using proguard, so it's not that easy to tell the exact method.

"main" prio=5 tid=1 MONITOR

| group="main" sCount=1 dsCount=0 obj=0x41d8bf80 self=0x41d785f0

| sysTid=6879 nice=0 sched=0/0 cgrp=apps handle=1073987200

| state=S schedstat=( 3859163490 373301317 3343 ) utm=287 stm=98 core=2

at wd.b(SourceFile:~275)

- waiting to lock <0x428bda30> (a java.lang.Object) held by tid=13 (AdWorker #3)

at xe.f(SourceFile:33)

at tj.p(SourceFile:522)

at tj.b(SourceFile:152)

at tt.onTransact(SourceFile:59)

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

at com.google.android.gms.internal.g.b((null):-1)

at com.google.android.gms.ads.f.a((null):-1)

at myApp.a.b((null):-1)

at myApp.myActivity.onDestroy((null):-1)

at android.app.Activity.performDestroy(Activity.java:5436)

at android.app.Instrumentation.callActivityOnDestroy(Instrumentation.java:1127)

at android.app.ActivityThread.performDestroyActivity(ActivityThread.java:3525)

at android.app.ActivityThread.handleDestroyActivity(ActivityThread.java:3556)

at android.app.ActivityThread.access$1300(ActivityThread.java:150)

at android.app.ActivityThread$H.handleMessage(ActivityT

...

[smrtp...@gmail.com]

How could I solve this????

...

[Eric Leichtenschlag]

There is a fix going out in the next release.

...

[smrtp...@gmail.com]

Hi Eric,

Good to hear that.

Is it possible to get ANR with an app if admob isn't called in a device? I mean, I have an app with admob and get ANRs from 4.0.3 if there isn't google play services in the device. Of coures admob fuctions aren't called then...

I really don't understand, I don't find any line in the traces which could point to my app... The emulator crashes... I've attached a log..

at android.os.Looper.loop(Looper.java:137)<br style="outline-color:rgb(76,184,202);font-family:monospace;line-height:18px

...

[Eric Leichtenschlag]

I don't even see the gms package anywhere in that ANR, let alone anything with the ads package. I think you may have a different issue.

at android.app.Activity.performCreate(Activity.java:4465)<br style="outline-color:rgb(76,184,202);font-family:monospace;line-height:18px;background-color:rgb(245,245,

...

[Fede Fdez]

Hi Eric, 

Please, can you confirm that this bug is fixed in Google Play services 4.3?.

Thanks

[Eric Leichtenschlag]

Yes, the fix went out in 4.3.

Thanks,
Eric

On Tuesday, March 18, 2014 1:12:54 AM UTC-7, Fede Fdez wrote:

Hi Eric, 

Please, can you confirm that this bug is fixed in Google Play services 4.3?.

Thanks</div

...

[Xavier Guillemané]

I haven't seen any improvment since the 4.3 version started rolling out last week.

I'm still having thousands of daily crash reports and it keeps increasing with new users installing the app...

[Bjørn Christian Seime]

You have to link your application with the updated SDK, which isn't available in SDK Manager yet.

[Xavier Guillemané]

Ok so without deploying another version of the app it won't be fixed ? I thought the deployment of the updated Google Play Services on the user devices was enough...

--

---
You received this message because you are subscribed to a topic in the Google Groups "Google AdMob Ads Developers" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/google-admob-ads-sdk/sePctoDJbRg/unsubscribe.
To unsubscribe from this group and all its topics, send an email to google-admob-ads...@googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

[Joaquin Grech]

any idea when the fix will be released? apparently this was fixed a few days ago but the sdk manager still doesn't show the update. The latest code i get in there is from february. Any way to get the google play services jar without having to wait for sdk manager?

To unsubscribe from this group and all its topics, send an email to google-admob-ads-sdk+unsub...@googlegroups.com.

[Eric Leichtenschlag]

New releases slowly roll out to devices, and the SDK doesn't become available from SDK manager until the rollout is complete. Complete rollout/new SDK from SDK manager should be available sometime this week if not today. The SDK manager is the only place to grab the new developer library.

The ANR fix however was done on the service side, so it should just be fixed automatically without you needing to update your apps for devices that have the Google Play store installed. For devices such as Kindles, they'll need to receive an app update with the new library in order to get the update.

Thanks,
Eric

[Xavier Guillemané]

In that case we should already see some impacts. And this isn't the case at all. The number of and and crashes is still increasing with new users...

To unsubscribe from this group and all its topics, send an email to google-admob-ads...@googlegroups.com.

[Eric Leichtenschlag]

I've actually been told that the rollout is a bit slower than I originally thought. Let's monitor this up until when the new SDK is available and see what the numbers look like.

To unsubscribe from this group and all its topics, send an email to google-admob-ads-sdk+unsubscrib...@googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

[Joaquin Grech]

ok so if i understood correctly... people will and must update their system so that this fix goes through???? I mean, that usually means no way!

why it did work with the previous sdk without problem and it fails now? from what you said, we should just roll back all our jar files and keep using the older system since it worked perfectly fine. If we depend on people updating the app/phone we are dead.

[Xavier Guillemané]

The Google play service update is pushed automatically on every device. You can compile your app with the latest version and force the user to update to the target version if you want to. Moreover the independent admob jar is deprecated and after in a 5 month it will be mandatory to use Google play services admob.

The main issue is: does the latest version fixes the issue? For now I don't see any improvement...

To unsubscribe from this group and all its topics, send an email to google-admob-ads...@googlegroups.com.

[Kevin Liu]

I believe google play services updates are pushed in the background to all devices logged in with a google account so the update speed is pretty reasonable. I think you're talking about an OTA update which indeed is a pain in the. 

[Joaquin Grech]

ok, that's great then. I was thinking we had to ask our users to update and that would be really really hard

[Dan Williams]

Yesterday I rolled out an update to use Admob from google play services. 

I have seen a few of these errors but it looks like I was lucky i released just when the fix is going out. I have seen a few errors but not thousands so it looks like the fix is being pushed out. 

[Xavier Guillemané]

The number of crash also depends on the number of screen views. As of now still no regression in the number of crashes...

Le 25 mars 2014 12:33, "Dan Williams" <danwm...@gmail.com> a écrit :

Yesterday I rolled out an update to use Admob from google play services. 

I have seen a few of these errors but it looks like I was lucky i released just when the fix is going out. I have seen a few errors but not thousands so it looks like the fix is being pushed out. 

--

---
You received this message because you are subscribed to a topic in the Google Groups "Google AdMob Ads Developers" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/google-admob-ads-sdk/sePctoDJbRg/unsubscribe.

To unsubscribe from this group and all its topics, send an email to google-admob-ads...@googlegroups.com.

[Bjørn Christian Seime]

I got a similar crash with a different signature just 3 hours ago:

java.lang.IllegalArgumentException: Service not registered: com.google.android.gms.common.i@42c675d8

at android.app.LoadedApk.forgetServiceDispatcher(LoadedApk.java:931)

at android.app.ContextImpl.unbindService(ContextImpl.java:1866)

at android.content.ContextWrapper.unbindService(ContextWrapper.java:515)

at com.google.android.gms.ads.b.a.a(Unknown Source)

at com.liquidm.sdk.AdvertisingIdCollector$1.run(SourceFile:61)

at java.lang.Thread.run(Thread.java:841)

 Same bug, new wrapping?

[Marcel Rocco]

Hi,

I am receiving this Error too. The top phone that I am receiving this is MOTO G (falcon_umtsds). It is not an ANR it is a Failure.
I will try this week to grab a Moto G to make some tests.

This update of Google Play Services will fix the error below?

java.lang.IllegalArgumentException: Service not registered: azc@421975c8
at android.app.LoadedApk.forgetServiceDispatcher(LoadedApk.java:926)
at android.app.ContextImpl.unbindService(ContextImpl.java:1606)
at android.content.ContextWrapper.unbindService(ContextWrapper.java:508)

at wr.a(SourceFile:135)
at tt.d(SourceFile:88)
at tt.b(SourceFile:129)
at tq.a(SourceFile:239)
at tq.a(SourceFile:176)
at zv.a(SourceFile:117)
at aay.run(SourceFile:14)
at aba.run(SourceFile:30)

at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1080)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:573)

at java.lang.Thread.run(Thread.java:841)

[Xavier Guillemané]

Good news, it looks like the crashes stopped a few hours ago!

To unsubscribe from this group and all its topics, send an email to google-admob-ads...@googlegroups.com.

[Stefano Baldi]

I keep getting exceptions
SecurityException (@Parcel:readException:1425) {AdWorker #2}

even after updating to rev 16

Less exceptions then before...but probably just because if a client has not an updated version of play services won't get ads

[Xavier Guillemané]

You don't have to build a new version of your app with the updated library. The issue will be fixed as soon as the user get the new GPS update.
Did you remove the call to destroy() to lower the number of ANRs? If so you need to re enable this call and everything should work fine.

[Stefano Baldi]

I didn't remove the call to destroy
Since i updated my lib reference to rev 16, users with rev 15 will not get ads (of this i'm sure)
So if i get an exception is from a user with an updated play services version
Am i wrong?

To unsubscribe from this group and all its topics, send an email to google-admob-ads-sdk+unsub...@googlegroups.com.

[Eric Leichtenschlag]

Stefano, do you have a full stack trace for the exception you're seeing?

The launch is 100% rolled out now. So if you only deploy your apps to the Google Play store, everybody will automatically be running rev 16.

Thanks,

Eric

[Stefano Baldi]

Hi Eric
Sorry i don't have a full stack trace, only that line i see from google analytics until someone sends me the full stack.
I can only add some info from analytics about the device and android version

SecurityException (@Parcel:readException:1425) {AdWorker #2}  Samsung GT-I9100 Galaxy S II  - Android 4.1.2
SecurityException (@Parcel:readException:1436) {AdWorker #2}  Xperia Arc HD - Android 4.1.2
SecurityException (@Parcel:readException:1327) {AdWorker #1}  Not Set - Android 4.0.3

[Eric Leichtenschlag]

Ok, we'll probably need a full trace to do more debugging but I'll make sure it's on our team's radar.

Thanks,

Eric

[Xavier Guillemané]

Any idea why my CTR dropped 20% and my eCPM 35% with the latest version of the Google Play Services?

I already got a 40% cut when updating from the old admob lib to the Google play services.

And now after 2 months of massive daily crashes this... Am I the only one seeing this drop?

To unsubscribe from this group and all its topics, send an email to google-admob-ads...@googlegroups.com.

[Eric Leichtenschlag]

Stefano,

You said "even after upgrading to rev 16". Does that mean you saw it in rev 15? When did you start seeing these crashes?

It's also tough to track this one down without a trace.

Thanks,
Eric

You received this message because you are subscribed to the Google Groups "Google AdMob Ads Developers" group.

To unsubscribe from this group and stop receiving emails from it, send an email to google-admob-ads...@googlegroups.com.

[Robert Richardson]

Hi Eric,

How late do you guys work?

Thanks,

Bob

[Stefano Baldi]

Hi Eric

I started seeing crashes after switching from admob jar to admob in play services, it was about a month ago.
And i keep seeing them after linking my apps to rev.16
I'm not 100% sure culprit is adMob since i have only a short description from analytics
And in simple apps, with no fragments or libs , i had no issues
I will wait some days to see if things settle down.
When you said rollout was complete i had new version on my nexus4 but a friend of mine on MotoG had old play services version
I guess even if rollout is complete will take some more time to see it installed everywhere

Thanks,
Eric

Eric

To unsubscribe from this group and all its topics, send an email to google-admob-ads-sdk+unsubscrib...@googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

--

---

You received this message because you are subscribed to the Google Groups "Google AdMob Ads Developers" group.

To unsubscribe from this group and stop receiving emails from it, send an email to google-admob-ads-sdk+unsub...@googlegroups.com.

[Eric Leichtenschlag]

I guess by "rollout complete" I mean that Android is not intentionally holding back the update on any devices. I'm not sure what happens if a device continues to stay offline or something, what the retry logic is for pushing out the update. Most users should have the update by now, and you should notice a different in crash count assuming the bug is fixed.

Thanks,
Eric

[yan MESS]

Hi Eric;

I am getting (yesterday) a SecurityException (android.os.Parcel.readException) 4 times from one device, i think that it happens with the latest update rev.16:

Galaxy Fame (nevis) Android 4.1 java.lang.SecurityException: attempting to read gservices without permission: Neither user 10131 nor current process has com.google.android.providers.gsf.permission.READ_GSERVICES. at android.os.Parcel.readException(Parcel.java:1425) at android.os.Parcel.readException(Parcel.java:1379) at xs.a(SourceFile:133) at xo.a(SourceFile:133) at xo.a(SourceFile:118) at ud.d(SourceFile:88) at ud.b(SourceFile:129) at ua.a(SourceFile:239) at ua.a(SourceFile:176) at aas.a(SourceFile:118) at abz.run(SourceFile:14) at acb.run(SourceFile:30) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1076) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:569) at java.lang.Thread.run(Thread.java:856) I also have an ANR that can be from ads: (android::AndroidRuntime::start(char const*, char const*)+390) #14 pc 00000dcf /system/bin/app_process #15 pc 00016e93 /system/lib/libc.so (__libc_init+38) #16 pc 00000b34 /system/bin/app_process at dalvik.system.DexFile.openDexFile(Native Method) at dalvik.system.DexFile.<init>(DexFile.java:109) at dalvik.system.DexFile.loadDex(DexFile.java:149) at dalvik.system.DexPathList.loadDexFile(DexPathList.java:261) at dalvik.system.DexPathList.makeDexElements(DexPathList.java:229) at dalvik.system.DexPathList.<init>(DexPathList.java:96) at dalvik.system.BaseDexClassLoader.<init>(BaseDexClassLoader.java:52) at dalvik.system.DexClassLoader.<init>(DexClassLoader.java:57) at tr.a(SourceFile:87) at tt.a(SourceFile:68) at xb.<init>(SourceFile:95) at xa.<init>(SourceFile:150) at com.google.android.gms.ads.AdManagerCreatorImpl.newAdManager(SourceFile:34) at xm.onTransact(SourceFile:66) at android.os.Binder.transact(Binder.java:326) at com.google.android.gms.internal.ad$a$a.a((null):-1) at com.google.android.gms.internal.u.b((null):-1) at com.google.android.gms.internal.u.a((null):-1) at com.google.android.gms.internal.ag.U((null):-1) at com.google.android.gms.internal.ag.a((null):-1) at com.google.android.gms.ads.AdView.loadAd((null):-1) at ...

The good news is that i stoped receiving the IllegalArgumentException related to AdMob.

Thanks,

Yan

[Stefano Baldi]

I'm getting same errors
thanks for the stack trace

[Xavier Guillemané]

Samething here... I'm having hundreds of those fatal errors since I build the app with the latest Google Play Service library.

FYI I'm not using any localization feature so this is a regression in the Admob library.

I hope you will be able to fix it soon. Users are getting tired of the app crashing because of the ad banner, and they start doubting my explanations

To unsubscribe from this group and all its topics, send an email to google-admob-ads...@googlegroups.com.

[Stefano Baldi]

Do you have webviews in your app?
Since i'm calling .destroy on activity destroy my crashes dramatically reduced
Maybe it's just a coincidence but today so far i had only 1 exception instead of 50 i got previously

Thanks,
Eric

To unsubscribe from this group and stop receiving emails from it, send an email to google-admob-ads-sdk+unsubscrib...@googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

--

---
You received this message because you are subscribed to a topic in the Google Groups "Google AdMob Ads Developers" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/google-admob-ads-sdk/sePctoDJbRg/unsubscribe.

To unsubscribe from this group and all its topics, send an email to google-admob-ads-sdk+unsub...@googlegroups.com.

[Xavier Guillemané]

As I explained yes the previous bugs are fixed but now there's a new major bug. The app is crashing because of a lack of permission related to the localization service which I don't use!

To unsubscribe from this group and all its topics, send an email to google-admob-ads...@googlegroups.com.

[Eric Leichtenschlag]

Hi Yan,

Thanks for the reports. The Security Exception came from Google Play services 4.3 and we'll take look at that one. The ANR trace is from Google Play services 4.2 when deobfuscated. so I'm still hoping that one is fully fixed in 4.3.

Thanks,

Eric