i have a problem using admob interstitial ads.i have done some searching and all i can find is that the error code that i am getting (code 3, the no fill error) means that there are no available ads to display. some say that ads will start appearing after a couple of hours but it has been a few days now and still ads are not appearing.
as far as i know i have set it up correctly. it works when i use the test ads but not when i use my live app id.
using the live app id on a real device returns ERROR_CODE_NO_FILL in the AdListener's onAdFailedToLoad() method but displays a test ad on the emulator. Nothing is displayed when the published app is installed from the google play store.
how can i get ads to display? or does this mean that ads will never be displayed
Related
I have an app that has had Admob integrated for years (so it's not a new ad spot).
I just updated Admob to latest "com.google.firebase:firebase-ads:17.1.1" from a previous verison, maybe 15 or 16 something. And consistently I am now getting this in logcat
Failed to load ad: 3 (No Fill)
No fill from any mediation ad networks.
1. If I add my device as a test device, I do get the test ad
2. If I download my app from the Play Store and try, I see ads are working (using the exact same interstitial/admob ID) so account is working...
I know I'm supposed to use test ads when in testing environment, but I'd like to see a live ad before pushing out an app update you know? Did Firebase change something to detect if it's not a "live" app?
(No code because it is the typical admob loading code which has been untouched, and as I said, test ads work)
As per the Documentation you are getting the following error code:
public static final int ERROR_CODE_NO_FILL
The ad request was successful, but no ad was returned due to lack of
ad inventory.
Constant Value: 3
Based on the post
onFailedToReceiveAd - Ad request successful, but no ad returned due to lack of ad inventory when using admob with adwhirl:
If you are getting this error, then your code is correct. The issue is
that AdMob does not always have an ad to return for every request.
This may happen particularly if you have just registered your AdMob
publisher ID, as it takes some time and multiple requests before the
new ID starts returning ads.
Another reason your fill rate may be low is that you don't have
AdSense backfill enabled, or you have filtered out some ads. Check
your app settings to see if that is the case.
Maybe you must try launch your app with other ip to get new ads.
I am new to using ad-mob and I created a simple app with ad-mob ad in it, and it's working fine except that it only shows only one and the same ad, I tried to close and open the app many times but still shows only one and the same ad.
This is normal. It could be due to a lack of ad inventory, meaning at that particular time at your geolocation, there are no other ads to serve besides the ad you keep seeing.
Also, check the app's ad settings in the admob console, to make sure "No refresh" is enabled. The ideal refresh rate should be 60seconds.
I was using AdMob to display their Ads in my android app and it was working great. I decided to try ad mediation with AdMob. I followed their guidelines, registered an account in InMobi and set up everything that I was supposed to (I guess). But now there is no difference in displaying ads. I mean I still get ads from google, and only from google (just like earlier). InMobi and AdMob show that I didn't generate any impressions and I have no idea what could have gone wrong.
For the record I changed my "ads:adUnitId" in layout, app was in market for more than 24h and generated some clicks, there is only one strange error in the LogCat (Failed to find provider info for com.google.plus.platform) and InMobi is printing some responses in LogCat.
Example response from InMobi:
InMobiAndroidSDK_3.6.2 : requestactivity=AdRequest&tp=c_gwhirl&u-rt=0&d-device-screen-density=1.5&d-device-screen-size=480X854&mk-siteid=a84ad8be300942ef8d356180085f8a41&u-id-map=uoJf3VOg5BXq327SMdvB5HwqkNA3jxHbj5FTAQhhpjIvzCnyMm%2BbQ3gGYv6%2BFukANGHv9uZdrfum%0AMcqlu8fqSw%3D%3D%0A&u-id-key=-991818964&u-key-ver=1&aid=bd3df942-9b44-49db-a8ed-798012f10bbb&mk-version=pr-SAND-DTGTC-20121219&mk-rel-version=3.6.2&format=xhtml&mk-ads=1&h-user-agent=Mozilla%2F5.0+%28Linux%3B+U%3B+Android+2.3.4%3B+en-gb%3B+LT18i+Build%2F4.0.2.A.0.62%29+AppleWebKit%2F533.1+%28KHTML%2C+like+Gecko%29+Version%2F4.0+Mobile+Safari%2F533.1&u-appBId=counterpicks.leagueoflegends&u-appDNM=LoL+Counter+picker&u-appVer=1.12&d-localization=en_gb&d-netType=wifi&d-orientation=1&mk-ad-slot=15
InMobiAndroidSDK_3.6.2 : Ad Response: <AdResponse><Ads></Ads></AdResponse>
So I guess that's a normal, working response.
No idea why mediation doesn't work.
It turned out that waiting 24h wasn't enough. After about 48h everything started to work.
Admob was showing ads on my application, everything was working fine. Then I created a new version of that app, uploaded it to google play and ads stopped appearing. In admob the status of this app chnaged to "Inactive: AdMob has never received an ad request for your site" (the bubble got from green to red) despite the fact that there is some revenue from the first version, when the ads were still working.
I didn't change adUnitId, it's the same like Publisher id shown in admob. When I run that app from eclipse test ads appear correctly, but only test ads. If I remove my device from list of test devices an ad is never displayed.
In LogCat I get these messages: Received ad url: "url" and then onFailedToReceiveAd(Ad request successful, but no ad returned due to lack of ad inventory.) Ok, it is possible that I don't get ads because of my locality or something, but how can that be with all few hundred people that used my app? The problem must be somewhere else.
What could be the problem? Do I need to create a new app in admob for every app update in google play store? (which seems unlogical to me)
Thank you.
I have had this issue once, and the admob moderation team had blocked my app. Maybe yours is blocked too.
I'm adding AdMob ads to my app. The test ad works fine in the emulator, but when I test it on a phone it doesn't display. Looking at LogCat, it says it received the ad, and it doesn't say that the space allotted is too small to hold the ad (I checked and it would tell me if that happened), but the test ad does not appear. I can't find any reason that the test ad would be successfully received and have enough space yet not be displayed, so I'm fairly stumped.
AdMob doesn't always show an AD.
The number of ads shown depend on how many requests you application make.
Few requests = few probability to see the banner.
Then if you doesn't receive any error and your logcat says that the ad is received correctly, then probably it is ok.
On my application installed on ~2000 devices the AD appears very rarely.