Jump to content
Can you post your code where you are initializing the plugin? Where you are calling the .show() function? And your build.settings? Please make sure that for each chunk of code you're sharing, click on the blue <> button in the row with Bold and Italic and paste your code into the popup window.
Rob, greetings, thank you for attending,
Basically the code that I am using is the one of the example.
You have to include the plugin in build.settings. You have to call the .init() API in main.lua with a listener function. This listener function should print out any responses from the server so you can know what's going on. Then depending on ad type, you will need to call the .load() api and the .show() api. You will have to provide both app and developer ID's that are properly configure in the AdMob portal.
Finally you have to test on a real device. Ads do not work in the simulator.
you need an "App ID" and at least one "Ad unit ID" (banner and/or interstitial and/or video, whatever, per your usage). those are the terms Admob itself uses. to find the App ID: Monetize, select app at left, expand the "view setup instructions". Ad units, and their ID's, are listed just below that
It's very important that you print out the response values in your adListener function. Then plug your test device into the USB port of your computer. For Android, you can use Android Studio or use the command line "adb logcat" command (may need to install the adb tools to use it). If you're on a Mac, Corona will magically route the device's console log to the Corona console log for you.
But until you see "why" AdMob is telling you it's not showing ads you're guessing in the dark.
Find out what's being reported please.
Community Forum Software by IP.Board