No fill even with test ads

[netl...@gmail.com]

Hi, I just launched a new app and I am not able to get even test ads to show up (error code 3, no fill). This is something that I've never seen before, usually with policy problems you still get test ads, but in my case not even those will work, all my other apps are working perfectly fine with AdMob. I have no policy violations and it says "Ad serving enabled" too, it is like I am shadow banned or something. I have been using AdMob for many years without any problems until now.

Are you able to please check it out and tell me what happened? It might be a bug in your system. I am 100% sure I haven't done anything wrong and everything is implemented correctly. I will reply with my ad unit ids privately when I get a reply from you.

Thank you!

[netl...@gmail.com]

It seems that not even the ad inspector will work with this package name id. This is the strangest thing I've ever encountered.

[Mobile Ads SDK Forum Advisor]

Hi,

Thank you for contacting the Mobile Ads SDK Support team.

No fill error means that the ad request was successful, but no ad was returned due to a lack of ad inventory. I ran Google Android sample applications with the test ads in the latest versions 23.4.0 and 23.5.0 and No fill is not replicating for me. Can you please confirm if the mentioned issue “No fill” is replicating in our Google Sample apps? If yes, Kindly provide the below details privately for further investigation:

• app ID
• ad unit ID
• SDK version used 

You can provide the following details via reply privately to the author option.

This message is in relation to case "ref:!00D1U01174p.!5004Q02vGjLz:ref" (ADR-00275185)

Thanks,
 

Mobile Ads SDK Team

[netl...@gmail.com]

Just sent you a private message now, I am using the latest AdMob version.

Thanks!

[Mobile Ads SDK Forum Advisor]

Hi,

Thank you for getting back to us.

Please note that new test devices typically start serving test ads in your app within 15 minutes, but it can also take up to 24 hours.

Upon checking your AdMob account, it was discovered that there is one test device (S10) registered. Additionally, it was observed that the Ad inspector gesture for the S10 is designated as "shake”. If the gesture is shake then after executing the project, shake the test device then the ad inspector is displayed on top of your apps as an overlay. You can also add a test device in your app programmatically using the Mobile Ads SDK request configuration. For more information, kindly refer to Test your app with ad inspector, Add a test device and Enable test ads. 

I have executed our Google Sample project with your PII information (app ID, ad unit ID and Package Name) and am unable to load the Ads on my end. Upon changing the Package Name, I am able to load the ads successfully on my end. Therefore, it appears that the root of the issue lies within your Package Name.

I would recommend that you reach out to the Product support team  as they are better equipped to address your concern.

[netl...@gmail.com]

Thanks for your reply! Are you sure this is not a bug on your side? There are no policy violations so it doesn't make any sense (and I know I didn't do anything wrong). I tried to reach out to support but it didn't seem like they know what is going on either, they're just saying "we're looking into it" and never get back. It seems like a bug to me, and I see somebody else posted the same thing here recently, it doesn't seem like a random coincidence.

Thanks