AdMob Android v6.4.1 sometimes causes ANR error?

[Kaam Deve]

AdMob Android v6.4.1 sometimes causes ANR error.

I use AdMob Android v6.4.1 in my Android game app, but sometimes it causes ANR error.

I use both AdMob Ads and AdMob mediation.

Both of them cause the same error.

I think AdMob SDK have these steps to show ads.

1:Ads: To get test ads on this device, call adRequest.addTestDevice("…");

2.Ads: adRequestUrlHtml

3.Ads: Received ad url

4.Ads: Ad url modified to

5.Ads: Request scenario: Online server request.

6.Ads: Caching gWhirl configuration for: 300 seconds

7.Ads: onReceiveAd()

But sometimes  AdMob SDK do only the 1st step below

Ads:To get test ads on this device, call adRequest.addTestDevice("…");

and do nothing more!

Whenever it happens,

when I kill the App, it causes ANR error and freeze.

Does anyone encounter the same situation?

Is it a bug in AdMob Android SDK v6.4.1?

I changed AdMob Android SDK from 6.4.1 to v6.1.0,

now this error never happens.

My Android devices' OS version is

Android 2.3

Android 3.2.1

The error messages when I kill App are below.

07-22 16:15:30.463: E/JavaBinder(300): !!! FAILED BINDER TRANSACTION !!!

07-22 16:15:30.463: E/JavaBinder(300): !!! FAILED BINDER TRANSACTION !!!

07-22 16:15:30.473: E/SensorService(300): dropping 1 events on the floor (Broken pipe)

07-22 16:15:30.493: E/SensorService(300): dropping 1 events on the floor (Broken pipe)

07-22 16:15:30.513: E/SensorService(300): dropping 1 events on the floor (Broken pipe)

07-22 16:15:30.533: E/SensorService(300): dropping 1 events on the floor (Broken pipe)

07-22 16:15:30.553: E/SensorService(300): dropping 1 events on the floor (Broken pipe)

the last line repeat forever!

Someone any idea?

It happens sometimes (about once in 30 tests), so I can't always reproduce it.

Thanks.

[Eric Leichtenschlag]

Hi Kaam,

Do you have a stack trace of the ANR prior to killing the app?

Other folks in this thread have complained about ANR introduced in v6.3.0, but we fixed (or attempted to fix) this in 6.4.1 and haven't heard any other complaints about it since it's release. Having another stack trace would help us figure out if/where the problem still exists on our side.

Thanks,

Eric

[Kaam Deve]

Hi Eric.

Sorry, there is no stack trace..

It never causes exceptions, just freeze.

I've already referred to that thread, but it's not the same.

I will wait for someone to post the same issue.

Thanks

2013年7月26日金曜日 5時24分03秒 UTC+9 Eric Leichtenschlag:

[Hermanto Kurniawan]

I got the exact same error

E/JavaBinder(300): !!! FAILED BINDER TRANSACTION !!!

E/SensorService(300): dropping 1 events on the floor (Broken pipe)

on my android 3.2.1. And it caused freezing without any other error message ( I used DDMS verbose)

Here's how I generate the error :
1. Run application with admob without internet connection
2. Try to load ad
3. Cancel loading ad with or without stopLoading then exit application
4. error message, freeze

Is there workaround for this? I'm using SDK 6.4.1

Thanks

[Michael Diener]

I'm also having this problem for devices running 2.3.*. It doesn't happen all the time, but only sometimes. The app then just displays a the title bar and everything else is black. The back button is not working, only the home button. Even when waiting for a while, there will be no "force close" dialog. Running in the adb shell a "kill -3 <pid>" will NOT produce a stack trace.

After killing the app through the app settings or "kill <pid>" it will start normally.

The devices this happen most of the time are Samsung Galaxy Ace and Galaxy Ace II. 

There are 2 stackoverflow threads that seem to describe the very same behaviour:

http://stackoverflow.com/questions/18163023/blank-screen-after-re-starting-launcher-activity-failed-binder-transaction

http://stackoverflow.com/questions/18252145/black-screen-after-restart

Both topics suggest to downgrade to AdMob 6.2.1 which I will try.

If anybody from AdMob needs help investigating this further, I'm happy to help, as I'm able to reproduce it though it takes some time until it appears.

Here some information from various logs:

<3>[24343.666412] binder: 6191: binder_alloc_buf, no vma

<6>[24343.666473] binder: 1504:10700 transaction failed 29201, size 300-4

<3>[24343.666839] binder: 6191: binder_alloc_buf, no vma

<6>[24343.666900] binder: 1504:10700 transaction failed 29201, size 92-4

6273    de.mdiener...             futex_wait_queue_me

08-29 18:40:35.187: E/JavaBinder(1504): !!! FAILED BINDER TRANSACTION !!!

When trying to reproduce the issue, I have encountered another ANR, which produced a stack trace. This might be the same issue, but oddly there was a "force close" dialog:

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=0x40022190 self=0xcec8

  | sysTid=25158 nice=0 sched=0/0 cgrp=[fopen-error:2] handle=-1345006496

  | schedstat=( 601684557 543884285 604 )

  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 com.google.ads.ak.f(SourceFile:354)

  at com.google.ads.ak.b(SourceFile:95)

  at com.google.ads.ak.a(SourceFile:69)

  at com.google.ads.n.<init>(SourceFile:158)

  at com.google.ads.internal.d.<init>(SourceFile:267)

  at com.google.ads.AdView.a(SourceFile:508)

  at com.google.ads.AdView.<init>(SourceFile:94)

[Konstantin Kolobov]

I have exactly the same problem with Admob 6.4.1. I have a bunch of ANR errors in my developer console and many user complains, and after a long investigations I was able to reproduce this bug on Samsung S5570 running Android 2.2.1. How to reproduce:

1) Admob banner should be loaded on application start with loadAd()

2) Phone should be connected to Internet through WiFi

3) I'm using NDK project

If I start app and click the Back button after 2-3 seconds (after loadAd call but before banner was actually loaded and displayed), then sometimes app hangs with ANR (after 20-30 attempts). And even the "Force Close" button in the ANR dialog is unable to close app! I can only close app in the Application Manager. 

I do not want to downgrade to Admob 6.2.1, because as I remember it has other problems (DexClassLoader ANRs).

Does anybody know a workaround? I tried to create my own "watch dog" thread, but it stops after calling exit(0) in C++ NDK. And app just hangs.

[Konstantin Kolobov]

Below is a log with ANR. It seems that ANR occurs ONLY if there is no "I/Ads(27123): adRequestUrlHtml: <html><head><script src="http://media.admob.com/sdk-core-v40.js">............................" string in the log (but adview.loadAd() was called before).

>>>>> application was started

09-27 13:44:07.000: ......................

09-27 13:44:09.065: D/Device Model(26792): GT-S5570

>>>>> Back button was clicked

09-27 13:44:09.835: I/KeyInputQueue(175): Input keycode=4 event: 1

09-27 13:44:09.835: D/KeyInputQueue(175): screenCaptureKeyFlag setting 1

09-27 13:44:09.835: I/WindowManager(175): Dispatching key to Window{4a8293e8 com.XXXX/com.XXXX.XXXX paused=false}

09-27 13:44:09.845: D/cocos2d-x debug info(26792): KernelApp: terminating bacause Back button was pressed

09-27 13:44:09.927: V/AudioFlinger(94): stop(4098), calling thread 94

09-27 13:44:09.927: V/AudioFlinger(94): (> STOPPED) => STOPPED (4098) on thread 0xbb50

09-27 13:44:09.927: V/AudioPolicyManager(94): stopOutput() output 1, stream 3

09-27 13:44:09.927: E/AudioPolicyManagerBase(94): unknown stream type

09-27 13:44:09.927: E/AudioPolicyManagerBase(94): unknown stream type

09-27 13:44:09.927: E/AudioPolicyManagerBase(94): unknown stream type

09-27 13:44:09.927: E/AudioPolicyManagerBase(94): unknown stream type

09-27 13:44:09.927: V/AudioPolicyManager(94): getNewDevice() selected device 0

09-27 13:44:09.927: V/AudioPolicyManager(94): setOutputDevice() output 1 device 0 force 0 delayMs 150

09-27 13:44:09.927: V/AudioPolicyManager(94): setOutputDevice() setting same device 0 or null device for output 1

09-27 13:44:09.927: V/AudioPolicyManager(94): releaseOutput() 1

>>>>> adView.stopLoading()

09-27 13:44:09.927: V/webview(26792): destroy : called.

>>>>> adView.destroy();

09-27 13:44:09.935: V/webview(26792): destroy : called.

09-27 13:44:09.945: V/AudioFlinger(94): remove track (4098) and delete from mixer

09-27 13:44:09.975: V/AudioFlinger(94): PlaybackThread::Track destructor

>>>>> android.os.Process.killProcess(android.os.Process.myPid());

09-27 13:44:10.015: E/JavaBinder(175): !!! FAILED BINDER TRANSACTION !!!

09-27 13:44:10.015: I/KeyInputQueue(175): Input keycode=4 event: 0

09-27 13:44:10.015: D/KeyInputQueue(175): screenCaptureKeyFlag setting 0

09-27 13:44:10.015: I/WindowManager(175): Dispatching key to Window{4a8293e8 com.XXXX/com.XXXX.XXXX paused=false}

09-27 13:44:12.947: V/AudioFlinger(94): Audio hardware entering standby, mixer 0xbb50, mSuspended 0

09-27 13:44:12.955: V/AudioFlinger(94): MixerThread 0xbb50 TID 151 going to sleep

09-27 13:44:16.018: W/PowerManagerService(175): Timer 0x7->0x3|0x0

09-27 13:44:16.018: I/PowerManagerService(175): Ulight 7->3|0

09-27 13:44:17.565: D/BatteryService(175): update start

09-27 13:44:17.595: D/BatteryService(175): updateBattery level:100 scale:100 status:5 health:2 present:true voltage: 4 temperature: 300 technology: Li-ion AC powered:false USB powered:true icon:17302197

09-27 13:44:17.605: D/KeyguardViewMediator(175): [hjin81.lee] Get ACTION_BATTERY_CHANGED

09-27 13:44:17.605: D/KeyguardViewMediator(175): [hjin81.lee] informBatteryStatus ~ battPlugged / battStatus / battHealth : true / 5 / 2

09-27 13:44:17.615: D/BatteryService(175): update start

09-27 13:44:17.625: D/BatteryService(175): update start

09-27 13:44:17.645: D/Tethering(175): active iface (usb0) reported as added, ignoring

09-27 13:44:17.645: I/WifiService(175): action : android.intent.action.BATTERY_CHANGED

09-27 13:44:17.645: D/WifiService(175): [mPersistState] : On

09-27 13:44:17.645: I/StatusBarPolicy(175): BAT. status:5 health:2

09-27 13:44:17.645: D/WifiService(175): ACTION_BATTERY_CHANGED pluggedType: 2

>>>>> clicking Back button again a few times

09-27 13:44:24.235: I/KeyInputQueue(175): Enqueueing touch event0

09-27 13:44:24.235: I/WindowManager(175): Read next event 0

09-27 13:44:24.325: I/KeyInputQueue(175): Enqueueing touch event1

09-27 13:44:24.835: I/KeyInputQueue(175): Enqueueing touch event0

09-27 13:44:24.890: I/KeyInputQueue(175): Enqueueing touch event1

09-27 13:44:27.045: I/KeyInputQueue(175): Enqueueing touch event0

09-27 13:44:27.100: I/KeyInputQueue(175): Enqueueing touch event1

09-27 13:44:27.565: D/BatteryService(175): update start

09-27 13:44:27.565: D/BatteryService(175): update start

09-27 13:44:27.575: D/BatteryService(175): update start

09-27 13:44:29.235: W/WindowManager(175): Key dispatching timed out sending to com.XXXX/com.XXXX.XXXX

09-27 13:44:29.235: W/WindowManager(175): Previous dispatch state: {{KeyEvent{action=1 code=4 repeat=0 meta=0 scancode=158 mFlags=8} to Window{4a8293e8 com.XXXX/com.XXXX.XXXX paused=false} @ 1380275050019 lw=Window{4a8293e8 com.XXXX/com.XXXX.XXXX paused=false} lb=android.os.BinderProxy@4a614848 fin=false gfw=true ed=true tts=0 wf=false fp=false mcf=Window{4a8293e8 com.XXXX/com.XXXX.XXXX paused=false}}}

09-27 13:44:29.235: W/WindowManager(175): Current dispatch state: {{null to Window{4a8293e8 com.XXXX/com.XXXX.XXXX paused=false} @ 1380275069240 lw=Window{4a8293e8 com.XXXX/com.XXXX.XXXX paused=false} lb=android.os.BinderProxy@4a614848 fin=false gfw=true ed=true tts=0 wf=false fp=false mcf=Window{4a8293e8 com.XXXX/com.XXXX.XXXX paused=false}}}

09-27 13:44:30.235: W/PowerManagerService(175): Timer 0x3->0x3|0x0

09-27 13:44:37.565: D/BatteryService(175): update start

09-27 13:44:37.565: D/BatteryService(175): update start

09-27 13:44:37.575: D/BatteryService(175): update start

09-27 13:44:44.235: W/WindowManager(175): Key dispatching timed out sending to com.XXXX/com.XXXX.XXXX

09-27 13:44:44.235: W/WindowManager(175): Previous dispatch state: {{KeyEvent{action=1 code=4 repeat=0 meta=0 scancode=158 mFlags=8} to Window{4a8293e8 com.XXXX/com.XXXX.XXXX paused=false} @ 1380275050019 lw=Window{4a8293e8 com.XXXX/com.XXXX.XXXX paused=false} lb=android.os.BinderProxy@4a614848 fin=false gfw=true ed=true tts=0 wf=false fp=false mcf=Window{4a8293e8 com.XXXX/com.XXXX.XXXX paused=false}}}

09-27 13:44:44.245: W/WindowManager(175): Current dispatch state: {{null to Window{4a8293e8 com.XXXX/com.XXXX.XXXX paused=false} @ 1380275084244 lw=Window{4a8293e8 com.XXXX/com.XXXX.XXXX paused=false} lb=android.os.BinderProxy@4a614848 fin=false gfw=true ed=true tts=0 wf=false fp=false mcf=Window{4a8293e8 com.XXXX/com.XXXX.XXXX paused=false}}}

09-27 13:44:44.835: E/ActivityManager(175): ANR in com.XXXX (com.XXXX/.XXXX)

09-27 13:44:44.835: E/ActivityManager(175): Reason: keyDispatchingTimedOut

09-27 13:44:44.835: E/ActivityManager(175): Load: 5.94 / 5.66 / 5.32

09-27 13:44:44.835: E/ActivityManager(175): CPU usage from 7356ms to 2353ms ago:

09-27 13:44:44.835: E/ActivityManager(175):   system_server: 11% = 3% user + 8% kernel

09-27 13:44:44.835: E/ActivityManager(175):   bma_wq: 3% = 0% user + 3% kernel

09-27 13:44:44.835: E/ActivityManager(175):   rild: 0% = 0% user + 0% kernel

09-27 13:44:44.835: E/ActivityManager(175): TOTAL: 16% = 4% user + 12% kernel

09-27 13:44:44.845: E/JavaBinder(175): !!! FAILED BINDER TRANSACTION !!!

09-27 13:44:44.845: I/WindowManager(175): Delivering pointer 0 > Window{4a8293e8 com.XXXX/com.XXXX.XXXX paused=false}

09-27 13:44:44.845: I/WindowManager(175): Read next event 1

09-27 13:44:44.875: W/WindowManager(175): No window to dispatch pointer action 1

09-27 13:44:44.875: I/WindowManager(175): Read next event 0

09-27 13:44:44.875: W/WindowManager(175): No window to dispatch pointer action 0

09-27 13:44:44.875: I/WindowManager(175): Read next event 1

09-27 13:44:44.875: W/WindowManager(175): No window to dispatch pointer action 1

09-27 13:44:44.875: I/WindowManager(175): Read next event 0

09-27 13:44:44.875: W/WindowManager(175): No window to dispatch pointer action 0

09-27 13:44:44.875: I/WindowManager(175): Read next event 1

09-27 13:44:44.875: W/WindowManager(175): No window to dispatch pointer action 1

09-27 13:44:44.925: E/JavaBinder(175): !!! FAILED BINDER TRANSACTION !!!

09-27 13:44:47.565: D/BatteryService(175): update start

09-27 13:44:47.565: D/BatteryService(175): update start

09-27 13:44:47.565: D/BatteryService(175): update start

09-27 13:44:50.285: D/VoldCmdListener(85): asec list

09-27 13:44:50.285: D/VoldCmdListener(85): CommandListener::AsecCmd::runCommand -> com.XXXX-1 

09-27 13:44:50.285: D/VoldCmdListener(85): CommandListener::AsecCmd::runCommand -> com.ZZZZ-1 

09-27 13:44:50.285: D/VoldCmdListener(85): CommandListener::AsecCmd::runCommand -> com.ZZZZ.sam-1 

09-27 13:44:50.285: D/VoldCmdListener(85): CommandListener::AsecCmd::runCommand -> com.ZZZZ.XXXX.paid.sam-1 

09-27 13:44:50.285: D/VoldCmdListener(85): CommandListener::AsecCmd::runCommand -> com.ZZZZ.XXXX.paid-2 

09-27 13:44:50.285: D/VoldCmdListener(85): CommandListener::AsecCmd::runCommand -> com.ZZZZ-1 

09-27 13:44:50.885: W/PowerManagerService(175): Timer 0x3->0x3|0x0

09-27 13:44:57.565: D/BatteryService(175): update start

09-27 13:44:57.565: D/BatteryService(175): update start

09-27 13:44:57.575: D/BatteryService(175): update start

09-27 13:45:07.565: D/BatteryService(175): update start

09-27 13:45:07.565: D/BatteryService(175): update start

09-27 13:45:07.575: D/BatteryService(175): update start

09-27 13:45:17.565: D/BatteryService(175): update start

09-27 13:45:17.565: D/BatteryService(175): update start

09-27 13:45:17.575: D/BatteryService(175): update start

09-27 13:45:27.565: D/BatteryService(175): update start

09-27 13:45:27.565: D/BatteryService(175): update start

09-27 13:45:27.575: D/BatteryService(175): update start

09-27 13:45:31.196: I/KeyInputQueue(175): Enqueueing touch event0

09-27 13:45:31.196: I/WindowManager(175): Read next event 0

09-27 13:45:31.196: I/WindowManager(175): Delivering pointer 0 > Window{4a865998 Sorry! paused=false}

09-27 13:45:31.288: I/KeyInputQueue(175): Enqueueing touch event1

09-27 13:45:31.288: I/WindowManager(175): Read next event 1

09-27 13:45:31.288: I/WindowManager(175): Delivering pointer 1 > Window{4a865998 Sorry! paused=false}

09-27 13:45:31.305: E/JavaBinder(175): !!! FAILED BINDER TRANSACTION !!!

09-27 13:45:33.175: E/JavaBinder(175): !!! FAILED BINDER TRANSACTION !!!

09-27 13:45:33.175: I/KeyInputQueue(175): Enqueueing touch event0

09-27 13:45:33.175: I/WindowManager(175): Read next event 0

09-27 13:45:33.175: I/WindowManager(175): Delivering pointer 0 > Window{4a8293e8 com.XXXX/com.XXXX.XXXX paused=false}

09-27 13:45:33.230: I/KeyInputQueue(175): Enqueueing touch event1

09-27 13:45:33.230: I/WindowManager(175): Read next event 1

09-27 13:45:34.335: I/KeyInputQueue(175): Enqueueing touch event0

09-27 13:45:34.415: I/KeyInputQueue(175): Enqueueing touch event1

09-27 13:45:37.565: D/BatteryService(175): update start

09-27 13:45:37.565: D/BatteryService(175): update start

09-27 13:45:37.575: D/BatteryService(175): update start

09-27 13:45:38.225: W/WindowManager(175): Key dispatching timed out sending to com.XXXX/com.XXXX.XXXX

09-27 13:45:38.235: W/WindowManager(175): Previous dispatch state: {{KeyEvent{action=1 code=4 repeat=0 meta=0 scancode=158 mFlags=8} to Window{4a8293e8 com.XXXX/com.XXXX.XXXX paused=false} @ 1380275050019 lw=Window{4a8293e8 com.XXXX/com.XXXX.XXXX paused=false} lb=android.os.BinderProxy@4a614848 fin=false gfw=true ed=true tts=0 wf=false fp=false mcf=Window{4a8293e8 com.XXXX/com.XXXX.XXXX paused=false}}}

09-27 13:45:38.235: W/WindowManager(175): Current dispatch state: {{null to Window{4a8293e8 com.XXXX/com.XXXX.XXXX paused=false} @ 1380275138235 lw=Window{4a8293e8 com.XXXX/com.XXXX.XXXX paused=false} lb=android.os.BinderProxy@4a614848 fin=false gfw=true ed=true tts=0 wf=false fp=false mcf=Window{4a8293e8 com.XXXX/com.XXXX.XXXX paused=false}}}

09-27 13:45:39.232: W/PowerManagerService(175): Timer 0x3->0x3|0x0

09-27 13:45:47.565: D/BatteryService(175): update start

09-27 13:45:47.565: D/BatteryService(175): update start

09-27 13:45:47.575: D/BatteryService(175): update start

[Michael Diener]

Hi Konstantin,

I might have an idea and currently test a workaround. So far it is working OK.

Could you post the parts of your code for onPause and onDestroy of your Activity? Only the parts regarding the AdView are interesting. I'd like to compare and see that what I suspect is right.

-Michael

[Michael Diener]

Nevermind, the issue still happens. I'm going to workaround this by including a different ad network for SDK level <= 10.

In any case I can confirm the steps to reproduce from Konstantin.

-Michael

[Konstantin K.]

Michael,

In the previous version of my game, I terminated process from non-UI thread with standard C function exit(0) (because I'm using NDK project).

As a workaround in new version, I will use android.os.Process.killProcess(android.os.Process.myPid()) from UI thread. Also, I will stop and destroy admob banner before killing process:

adView.stopLoading();

((ViewGroup)adView.getParent()).removeView(adView);

adView.destroy(); 

May be this will help to fix the bug, at least I'm unable to reproduce it anymore (but I was testing without DDMS logging and in release build).

[Oleg Morozov]

Konstantin K. 

I have the same problem.

Details: http://stackoverflow.com/questions/18735790/android-application-doesnt-close-after-calling-system-exit0

I think I tried everything. I'm searching for earlier release of admob sdk now. Could you tell me, where can I download admob-6.3.1.jar?

четверг, 25 июля 2013 г., 17:59:41 UTC+3 пользователь Kaam Deve написал:

[Konstantin K.]

I still have problems with Admob 6.4.1 in my apps. In the last version of my apps, I added this code

adView.stopLoading();

((ViewGroup)adView.getParent()).removeView(adView);

adView.destroy(); 

before killing process with android.os.Process.killProcess(android.os.Process.myPid()), but I still see ANR reports in the developer console.

It will be good if someone from Admob team provides us with a workaround. I can reproduce this bug on Samsung S5570 and I can provide any logs / do any experiments if needed. Most of negative comments/ratings for my apps are because of this bug.

-- Konstantin

[Алексей Чекин]

Today I also got the problem:

 

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

"main" prio=5 tid=1 SUSPENDED
| group="main" sCount=1 dsCount=0 obj=0x4170d9a0 self=0x400fd010
| sysTid=980 nice=0 sched=0/0 cgrp=apps handle=1075155932
| state=S schedstat=( 254266875 156637875 399 ) utm=11 stm=14 core=1
at android.util.SparseArray.binarySearch(SparseArray.java:~343)
at android.util.SparseArray.get(SparseArray.java:82)
at android.util.SparseArray.get(SparseArray.java:73)
at android.content.res.StringBlock.get(StringBlock.java:69)
at android.content.res.AssetManager.getResourceValue(AssetManager.java:201)
at android.content.res.Resources.getValue(Resources.java:1010)
at android.content.res.Resources.getDrawable(Resources.java:659)
at android.widget.EdgeEffect.<init>(EdgeEffect.java:137)
at android.webkit.OverScrollGlow.<init>(OverScrollGlow.java:45)
at android.webkit.WebViewClassic.setOverScrollMode(WebViewClassic.java:1805)
at android.webkit.WebView.setOverScrollMode(WebView.java:1917)
at android.view.View.<init>(View.java:3254)
at android.view.View.<init>(View.java:3298)
at android.view.ViewGroup.<init>(ViewGroup.java:431)
at android.widget.AbsoluteLayout.<init>(AbsoluteLayout.java:52)
at android.webkit.WebView.<init>(WebView.java:504)
at android.webkit.WebView.<init>(WebView.java:481)
at android.webkit.WebView.<init>(WebView.java:461)
at android.webkit.WebView.<init>(WebView.java:450)
at android.webkit.WebView.<init>(WebView.java:440)
at com.google.ads.util.a.i((null):-1)
at com.google.ads.util.a.a((null):-1)
at com.google.ads.internal.e.<init>((null):-1)

[Shane Doyle]

I am facing the same issue on v6.4.1. Has anyone found a solution to the problem?

[Stefano Bonetta]

I think I've found a "solution".

Edit the method onInvalidate() in the file com.mopub.mobileads.GoogleAdmobBanner.java, just change

      mAdMobView.destroy();

to:

      mAdMobView.postDelayed(new Runnable() {

@Override

public void run() {

mAdMobView.destroy();

}

}, 200);