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.
One of the suggested fixes in the StackOverflow posts was to be logged in to G+. I’m assuming that since Google tries to do a single signon, that being logged in to GPGS would count.
Rob
Great finding!
Corona should take a note about it into the bug report and try to find out the “initilization” that can fix this problem.
As stated by ingemar :
I’ve reported bug (3) First banner not shown.
Case 32594
Any progress?
Thanks - MAS1.
We are still investigating.
Does this v2 version have anything that allows us to know when an Interstitial is closed so we can start the banners again? I’m having problems with the v1 plugin not showing both at the same time. I had it working, but now it isn’t anymore. If I try to do both, (i relaunch banner after interstitial since it kills it) it just causes both to stop. The banner being called right after interstitial breaks interstitial by aborting it before it shows and then banner never turns back on.
It would be best to send an official bug report if you haven’t already done so.
That way CoronaLabs can prioritize and schedule a fix.
how does one access this v2 plugin? is it through daily builds or something else?
edit:
nvm, found it: http://docs.coronalabs.com/plugin/ads-admob-v2/index.html
I will also do some testing and see how this works, crossing fingers 
After more testing I can confirm the ad height works great for portrait (landscape still to be tested).
Also, the FPS bug seems to be dead (yeah!).
Now please only fix the new bug so we can release our new game with this version and also replace it in all of our games.
Thank you!
Regards,
Damir.
Did you submit a bug report for the new bug?
I just keep getting:
"[Build Error #5]
A device build error occurred on the server.
BuildID: <irrelevant>
Error: Get plugin failed.
Publisher: com.coronalabs
Plugin: plugin.google.play.services"
plugins section of build.settings straight from here:
http://docs.coronalabs.com/plugin/ads-admob-v2/
build 2014.2189
builds fine with “original” admob plugin
ideas? thx
Can you post your build.settings file?
This version of the plugin uses the new version of the Admob SDK. It will only work with build 2014.2264 or later.
No.