I alerted engineering to this yesterday, but based on posts on Stack Overflow, this seems to be a bug in the Google SDK and I don’t know that there is a work around that we can do, other than watch for Google to release an update to their SDK and have us re-compile the plugin.
Just for fun has any one tried ad.show();ad.hide();ad.show() or some other technique to get the first ad out of the way?
Rob
Hi Brent,
yes the build error on iOS is fixed.
Also, there is no “first ad now shown” bug on iOS.
Can you confirm this bug is Goggles fault and not Corona Labs?
Hi Damir,
A simple way to confirm this is to google: admob not showing first ad
There are frequent complaints about this problem from the native app developers. There are several suggestions on work arounds for this, like bringing the view to the front, tweaking the background color, being logged into G+, etc. There is another forum thread that I alerted engineering to last night:
http://forums.coronalabs.com/topic/38495-admob-problem/#entry245275
But being the weekend, I wouldn’t expect them to see it until Monday at the earliest. But there isn’t a bug report that I’m aware of on this and I’ve asked for one to be filed. There might be a work around that works if it’s not too much of a hack. I’d still like to see someone try to do a show(), hide() and show() again on the first time to see if that works.
Rob
I’d still like to see someone try to do a show(), hide() and show() again on the first time to see if that works.
The sample project I submitted with the case above has a button where you can hide/show the ad.
Show/hide/show doesn’t fix the issue. If fact, every “first” show will make the ad invisible. What I mean is if you wait for the second ad to make the ad visible (*note1), and then press hide to hide it, the next time you show the ad it’s invisible again and you have to wait for the second ad to unhide it.
(*note1) You can also force the ad to become visible by turning the device off/on.
Sorry to report again, but the plugin does not work.
It works in our landscape game but in the portrait game the banners are not shown (they work with the adMob v1 plugin).
The ADB console gives this:
06-14 17:12:37.554: W/Ads(26636): Not enough space to show ad. Needs 601x90 pixels, but only has 600x976 pixels.
Here is the config.lua if it helps:
application =
{
content =
{
width = 480,
height = 800,
scale = “letterbox”,
},
}
Regards,
Damir.
Please file a bug report for this.
Thanks
Rob
I am not seeing the banner ad showing up in my Android device either when I use admob-v2
I saw it once but I don’t see it any more, no matter how many times I call ads.hide() & ads.show()
When I changed it back to earlier admob plugin, I can see the banner ad.
So for v2, except ads.height(), what other new features or enhancements are in it? Why should I use v-2 after all?
Weird. I was just updating an app, and tested Admob-V2 about an hour ago and ads show up.
On thing though. When I logged in to Admob today, they said that the new Admob was available and wanted me to upgrade.
It’s connected to AdSense/AdWords now. I upgraded and the apps get a new id (really long one). The older (shorter) legacy id’s should still work though.
I updated my app to use the new long id’s, and that’s what I’m currently testing.
is your last message for me?
I don’t get it… you mean you can see the ad now? I thought you just filed a bug report for this first-banner-not-shown problem?
I just saw you said “You can also force the ad to become visible by turning the device off/on.”, so I tried to turn off/on the device, like you said, I can see the ad.
But it still doesn’t show up after my scene change that calls ads.hide() & ads.show() again.
Anyway, I mean I am still seeing this problem consistently.
The problem is that the “first ad not shown” issue is not always present. I reported a test-case where is was reproducible, however this particular app I’m updating has never had that problem, and I can’t replicate the issue in a test case.
The only difference I see is that I use several ads.* API providers. iAd, Vungle and Admob. I’m also using a proprietary ad-network module to dynamically switch between the providers. Maybe my switching between the providers somehow “fixes” the problem.
I’m using today’s new build 2300 for my testing.
In your previous post I was assuming that you all of a sudden couldn’t see any ads at all with Admob V2. Even after the refresh period…
I also upgraded to new Admob interface and tried with the “long id” you referred to. The ad is still not showing in my Android device, so I gave up.
Doesn’t the ad show even after the first refresh period?
You asked why V2? The reason is that Google will stop accepting new apps or updates that use the old Admob API starting Aug 1 2014.
Thanks a lot for the v2 deadline info.
I didn’t really try to see if the ad would show after the first refresh period,
because it’s a BIG bug already if it’s not showing even if it will show after the first refresh period.
If it does not show up before the first refresh period, why would anyone use it at all?
There seems a new version of Admob SDK, has Corona updated to use it to see if the problem goes away? and what’s the plan for this bug? any chance that it’s Corona’s responsibility or totally Google’s?
I was able to reproduce the issue, which is why I reported it.
Although I’ve seen this issue being discussed on other forums for native Android programming, so I think it might be an Android thing.
https://groups.google.com/forum/#!topic/google-admob-ads-sdk/avwVXvBt_sM
It doesn’t say it’s the SDK problem, and people are offering solutions by tweaking Android code, which in turn is something Corona should also try to work out.
That’s true. Plus the fact that my Corona app I’m testing on has no problems!
It always shows the first ad…
The *only* difference is that it’s an Enterprise app. The test app where I was able to reproduce the problem uses the standard Corona Simulator build. I’ll convert it to Enterprise and see if it makes a difference…
Nope… Enterprise didn’t make any difference. Still no first ad shown in the test app.
As for my other app. I’ve deactivated all adnetworks except admob in my adnetwork module, and the first ad still shows there.
I’ll try to find out why my own adnetwork module gets around this issue…
Sounds very odd… are you sure you are using v-2 in your the other app that works?
do you happen to include admob-v1 plugin again? (I had done this before, v-1 will override v-2 in my recall)
It’s very odd indeed.
I’m using Enterprise and I’ve double-checked that all references to the old Admob libraries are gone. I can also get the height of the ad which confirms it’s using the new library.
I just can’t understand why it works with this particular app.
FINALLY!
I figured out why my app shows an Admob ad on the first call to ads.show(“banner”).
I’m using Google Play Game Services for leaderboard management (gameNetwork.* API), and there’s something within the initialization of that library which “fixes” the problem. When I remove the gameNetwork code from my app, the first ad is *not* shown until after the first refresh.
Note to other readers: This only affects Android devices, iOS behaves as it should.