Version: Next

Troubleshooting

First Step

Run the following command in your project root directory,

npx admob-plus doctor

This will scan for common errors and provide suggestions how to fix them.

Make sure you have listen to error event and log the fail reason, ads may fail to load for various reasons.

Beside programming error, a common report is no fill error (explanation post), which many users think it is the problem of the library.

It is common that for the first time requesting newly created ad unit, there is a delay to have available ads start serving.

Also, some country or targeted deivce could have less ads to serve due to publisher / user settings.

Problem	Answer
Did you recently create your AdMob account?	Wait up to 24 hours after you create your account.
Is your app or ad unit new?	Wait up to one hour after you create an app or ad unit. In some cases, it can take a few days for ads to appear in new apps or ad units. Note: New iOS apps will not show Google ads until they’re listed in the Apple App Store.
Have you integrated the Google Mobile Ads SDK correctly?	Take a look at the examples.

First of all, make sure your Ad request and display code are correct.

The Ad server may not have ads to serve for every request, which returns NO_FILL response.

It is receommended to track the impressions via event API instead of just the API calls, as it is not necessary result in showing Ads.

It is likely you have violated some of the policies, one is common that you are not using Test Ads during development, see AdMob & AdSense program policies - Invalid traffic.

Another reason could be displaying ads in a way that is not appropriated, see Disallowed interstitial implementations.