I use that plugin too and it works well.
Remember to call the plugin after deviceready event fires and call both createBannerView and requestAd functions.
The “thing” about isTesting , is that if you click an ad when testing:true, you won’t be “punished” for doing that. In real life, if you click your own ads you can be “punished” for doing that .
But my problem is that it doesn’t show any ads… It always shows me a black box, and nothing else .
How do you manage to make it work? Can you help me or show me what you have done? @gki , I will really appreciate it.
I do use the first plugin you mentioned, and it works for me. The code is like yours, so there must be something else wrong.
Have you installed google play service plugin?
You can also try to see the log with adb logcat, maybe you notice something strange…
Yes, I installed google play service plugin, but it is not working… I tried everything and I continue seeing a black box… I tried also what @gki post, and it’s not working for me… frowning
Try adb logcat to see if there is some error or such.
I usually do something like adb logcat | grep --line-buffered -i -e ads -e admob to see in realtime log messages related to ads or admob, then lunch the app.
Sorry, grep only works in linux, I don’t know what is the equivalent in windows if you are using it.
Anyway, it seems that somewhere you are trying to call .showAd() function of something that does not exist (undefined). You should call it on window.plugins.AdMob.
Despite your code seems correct, try replace am.showAd(true) with window.plugins.AdMob.showAd(true) and make sure you are not calling showAd somewhere else.
If you want to debug a little further you can also try with Weinre.