Why "Don’t fill the advertising server. Failed to load the ad: 3" to stop advertising requests?

Question

I applied firebase declarations, as in exampe :

@Override public void onCreate(Bundle savedInstanceState) { (...) mAdView.loadAd(adRequestBuilder.build()); } @Override public void onResume() { mAdView.resume(); } @Override public void onPause() { mAdView.pause(); } @Override public void onDestroy() { mAdView.destroy(); } 

If the ad has been successfully downloaded or not completed due to the lack of an Internet connection (errorCode 2), it will still be updated:

I / Ads: Planning for an ad update with 60,000 milliseconds.

We get the same message when we go background, and then foreground ( mAdView.resume() , mAdView.pause() ).

But if we get "no fill"

Do not populate the ad server. Failed to load ad: 3

firebase stops requesting new ads. This means that the user will not see new ads (or even the first if the first request is completed with "no fill"). In addition, if the application goes into the background, then the foreground ( mAdView.resume() is called), the ad request will still not be executed. This means that the user who received "no fill", for a long time does not see ads. It can lower my income.

Is this ad library behavior correct or is it a bug? How to solve this problem?

---

Update

I have one idea. Moving the mAdView.loadAd(adRequestBuilder.build()) onCreate() from onCreate() to onResume() forces the advertisement to reload when the user returns from the background.

 @Override public void onResume() { if (!mAdView.isLoading()) mAdView.loadAd(adRequestBuilder.build()); mAdView.resume(); } 

What is interesting after many tests is the call to mAdView.loadAd(adRequestBuilder.build()) after No fill from ad server. Failed to load ad: 3 No fill from ad server. Failed to load ad: 3 forces the ad to reload (I get the message: Starting ad request. ), But it never ended successfully. I still get No fill from ad server. Failed to load ad: 3 No fill from ad server. Failed to load ad: 3 . And the answer is very quick. I guess it comes from its local cache.

Answer 1

Contact: How to find out if an AdMob ad has been uploaded

Remember the Firebase methods when you get onFailedToReceiveAd ().