banner load fail, got an error message, hope someone can help

[AcShadow]

this is the error message returned.

{"isTrusted":false,"error":3,"reason":"No Fill","adType":"banner"}

also none of the ads are using testing ads. this worries me to continue testing. here is the code:

admob.banner.config({
     id: 'myCode',
     isTesting: true,
     autoShow: true,
     overlap: true
    });
    admob.banner.prepare();

document.addEventListener('admob.banner.events.LOAD_FAIL',function(event){
        alert("load fail: "+JSON.stringify(event));
    });
    document.addEventListener('admob.banner.events.LOAD',function(event){
        alert("load good"+JSON.stringify(event));
        alert(JSON.stringify(admob.banner.config.id));
    });

just to be clear, the LOAD_FAIL event is firing every time. consistently. I am able to display interstitial ads fine but they are not testing ads even after i set the config to isTesting: true

[erperejildo]

Similar issue? https://github.com/ratson/cordova-plugin-admob-free/issues/119

[AcShadow]

i tried some of the solutions listed on that issue but none worked. I created a new cordova android project to test with just this plugin and i was still having issues. Then on a whim i changed the id of my banner ad to the id listed in your example for the banner, it works perfectly.... I then created a new banner ad and its not working. how am i creating ad units incorrectly?

[AcShadow]

ok so i messed around with the settings on admob for my banner ad unit, turns out automatic refresh was causing this issue or at least somewhat related as i had it on the setting "google optimized" and after changing to "disabled" the banner ad now displays. BUT it is still not in testing mode.

[AcShadow]

Shall i close this issue to create a more accurate version?

[romit19]

@acshadow i am also facing same issue. could you please elaborate.

[NeoHoffa]

Same issue here. I followed this tutorial https://www.npmjs.com/package/cordova-plugin-admob-simple

But running on iOS. I'm getting the same error on the "onFailedToReceiveAd" callback that shows..

{"isTrusted":false, "error":"Request Error: No ad to show."}

[manjunath-K]

getting same issue. I have created admob account and created ad unit, when tested getting below error.

{"isTrusted":false,"adNetwork":"AdMob","adType":"banner","adEvent":"onAdFailLoad","error":0,"reason":"Internal error"} when i tested with google test ad unit the code is working properly. not able to understand please help

[manjunath-K]

Hi, I resolved the above issue. seems like to active the ads admob or google service taking some time to configure. I didn't change any code. after 6 hours tested, now loading the banners successfully. I searched for the active unit status on admob panel and google console panel but didn't find anywhere. I think this is the reason why we are not getting the ads immediately. please check after some time you may get.

[shinobirozs]

@manjunath-K , I'm also experiencing the same issue on one of my apps right now. How did you fix it?

onFailedToReceiveAd : reason:"No Fill"

Thanks in advance.

[manjunath-K]

Hi ShinobiRozs, yes, the No Fill comes when there is no ads, you don't need to do any thing when there are ads that will show, you make sure your code is correct, to check display check with google ads id's.

On Tue, Dec 18, 2018 at 5:44 PM ShinobiRozs [email protected] wrote:

@manjunath-K https://github.com/manjunath-K , I'm also experiencing the same issue on one of my apps right now. How did you fixed it?

onFailedToReceiveAd : reason:"No Fill"

Thanks in advance.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/ratson/cordova-plugin-admob-free/issues/173#issuecomment-448200646, or mute the thread https://github.com/notifications/unsubscribe-auth/AFEn5wUtbnRGNTgT08522VoderjnKP0Xks5u6Nw0gaJpZM4SRLNJ .

[shinobirozs]

@manjunath-K, Thank you. I am really grateful to you for your prompt reply.

[osmaneser]

aren't there are solved anybody this problem? I'm going crazy.

[lucydjo]

Up.

[carlosbeperaza]

@osmaneser any update about the problem?