AdMob banner ad loaded twice when clicked, even in example app by Google

[Cristian Perez]

When I click an AdMob banner ad in my Android application, the ad URL is opened and displayed, and then about 5 seconds later, the same URL is opened again.

This is an extremely strange bug I don't know why could be happening. Thought it was my fault, but the same is happening with this minimal example by Google (download, import and run BannerExample_AdMob.zip).

It happens all the time, and it's really annoying, as it results in two Chrome tabs with the same ad being shown. And if you don't have a default app for opening http intents, it results in two "Open with..." dialogs being opened with 5 seconds of difference, which feels like something is broken.

This is the very relevant log by AdMob. Only one click was performed on the ad, and as you can see "Ad opening" happens two times without reason:

12-13 17:30:27.919 I/Ads﹕ Starting ad request.
12-13 17:30:27.920 I/Ads﹕ Use AdRequest.Builder.addTestDevice("XXXXXXXX") to get test ads on this device.
12-13 17:30:30.406 I/Ads﹕ Ad finished loading.
12-13 17:30:30.424 I/Ads﹕ Scheduling ad refresh 60000 milliseconds from now.
12-13 17:30:35.076 I/Ads﹕ Scheduling ad refresh 60000 milliseconds from now.
12-13 17:30:40.107 I/Ads﹕ Ad opening.
12-13 17:30:40.119 I/Ads﹕ Ad leaving application.
12-13 17:30:45.286 I/Ads﹕ Ad opening.
12-13 17:30:45.292 I/Ads﹕ Ad leaving application.
12-13 17:30:45.302 I/Ads﹕ Ad closing.

I have reproduced this issue both with test and real ads, and in different real devices (Nexus 5 with Android 5.0 and Galaxy S5 with Android 4.4). I have also tried with several different versions of Google Play Services, from 4.x up to the latest 6.x, with the same result.

Any help would be appreciated, including feedback on whether you are able to reproduce the issue with the example app, which takes 2 minutes to try. Huge thanks.

[Andrew Brogdon (Mobile Ads SDK Team)]

I don't know why you're getting that behavior from your application.  I just downloaded a fresh copy of the banner example for AdMob, built it, and did not see the result you describe.

Is there anything unusual about your particular setup or network?  Have you tried connecting over 4G instead of WiFi (or vice versa) or moved to a different network?  Was all of this development done on the same machine?

-Andrew

[Spencer]

Dear Cristian

The way you do, I think right in some port.

Not sure, but you have to change one of your code.

your code : 

            "     adRequest = new AdRequest.Builder().addTestDevice(AdRequest.DEVICE_ID_EMULATOR).addTestDevice("3D87890811D11897D192064D2D301B8D").build();           "

change to : 

            "     adRequest = new AdRequest.Builder().build();           "

But if you want to have real AD on your Phone, Please don't do that

At any reason, It is strictly prohibited by policies.

If you are starter of Admob, Here is App for you.

The Key words is "How to admob" in Play Store.

There will be "AdMob ads How to add in my App" :

 Links : Admob ads How to add in my App

spencer

2014년 12월 14일 일요일 오후 9시 38분 17초 UTC+9, Cristian Perez 님의 말:

[Cristian Perez]

Thanks Andrew,

I just tried it again and now it works okay. I noticed that there probably was a server-side AdMob change. In all my trials, the first touch on the ad showed a blue confirmation button to visit the ad. Now it doesn't, and the problem is gone. So probably it was a bug due to the introduction of this "feature", and they already noticed it and reverted it: http://appdevelopermagazine.com/147/2012/12/14/Admob-adds-a-confirmation-prompt-in-ads/

Let me know if I could be right. Thanks,

Cristian