Bug: getting message: "The Google Mobile Ads SDK will not integrate with Firebase"

[Liran Barsisa]

Ever since yesterday, I can't show Admob ads on my device anymore.

I have done it using the old API on one app I have (here), and using the new Firebase one on another.

The only thing I get, is a very short log message as such:

10-13 14:00:19.325 32451-32503/? W/Ads: The Google Mobile Ads SDK will not integrate with Firebase. Admob/Firbase integration requires the latest Firebase SDK jar, but Firebase SDK is either missing or out of date

The gradle configurations are of the latest available, and it works fine on another device (works on HTC One M8 with Android 7.1, but not on my Nexus 5x with Android O).

Here are the configurations:

old API:

    compile 'com.google.android.gms:play-services-ads:11.4.2'

new API:

    compile 'com.google.firebase:firebase-ads:11.4.2'

How could this be?

[Liran Barsisa]

The error code I get from onAdFailedToLoad is 3, which is "ERROR_CODE_NO_FILL" :

https://developers.google.com/android/reference/com/google/android/gms/ads/AdRequest.html#ERROR_CODE_NO_FILL

[Liran Barsisa]

After I've reset Google Play Services, it's back to normal. Now it works fine.

Please fix this issue.

[Bharani Cherukuri (Mobile Ads SDK Team)]

Hello, 

Thank you for contacting us. Could you provide us the complete device logs when the error is experienced? Please note that ERROR_CODE_NO_FILL error is noticed when there is no ad returned from the ad server due to lack of ad inventory. Could you provide us the Ad Unit ID used, so we can take a look and assist you further?

Additionally, do look out for an email from us requesting your Ad Unit ID privately.

Regards,

Bharani Cherukuri

Mobile Ads SDK Team 

[Liran Barsisa]

Attached here bug report file.

However, as I wrote, the workaround has fixed it (of clear-data of play services), and what I sent now is a few hours after I've fixed it (also restarted the OS).

The no-fill error doesn't make sense. It always showed me an ad before, and when I got the error, I always had it. I could reproduce it over and over again, on both apps, which have different ad-unit-id.

I think the bug is on the play-services.

About the ad-unit-id, the newer one (that I used with Firebase ads sdk) is this:

ca-app-pub-5364258156299848/3929261218

Hope this helps.

[Liran Barsisa]

Note that originally, I use the newer app to show only full screen ads, and not banners. However, for the test, I created a new Activity that shows just a banner. It worked on another device, but not on mine.

[Bharani Cherukuri (Mobile Ads SDK Team)]

Hello Liran,

Thank you for the additional details. Based on the description, it looks like there might be an issue with the old package name that you were using. I was able to load ads with the new Ad Unit ID using our sample apps. To resolve the issue with your old package name, you can reach out to the AdMob Product Support Team via the Contact Us button on the upper right hand corner of this page. Make sure to login with your Gmail/AdMob account to access the support page.

Regards,

Bharani Cherukuri

Mobile Ads SDK Team

On Friday, October 13, 2017 at 7:16:31 AM UTC-4, Liran Barsisa wrote:

[Liran Barsisa]

What do you mean "an old package name"?

Old package name of what?
Both apps work fine on the other device, and on other devices I've tested.

Only on my Nexus 5x it didn't work, and after I've reset the Play Services app, it got fixed.

[Bharani Cherukuri (Mobile Ads SDK Team)]

Hello Liran, 

Glad to hear that your issue has been resolved and you are able to load ads on both the apps. As for your concern about the package name, sometimes, there might be an issue with the package name, resulting in a no fill from the ad server. Since resetting the Google play services fixed the issue on Nexus 5x, it could be a device specific issue which is blocking ads from serving.

Should you have any other concerns, feel free to get back to us and I will be happy to assist you.

Regards,

Bharani Cherukuri

Mobile Ads SDK Team

On Friday, October 13, 2017 at 7:16:31 AM UTC-4, Liran Barsisa wrote:

[Liran Barsisa]

The issue is NOT resolved.

Otherwise, why would I have written "Please fix this issue." ...

It's just that I've found a workaround, as a USER. Not as a developer. As a developer, I saw that the ads aren't showing anymore. As a user, what i did is to reset the Play-Services. No real user will do such a thing, especially to show ads.

And again, what do you mean "there might be an issue with the package name" ? What package name? I'm talking about 2 apps that work fine on the Play Store, with the exact same package name as before (I can't change package name anyway), on one device, yet on the Nexus 5x both of the apps failed to show ads.

This clearly shows that something is wrong in the SDK or on the Play Services.

The device isn't blocking ads. I didn't install any such app or modified the OS in such a way. Not only that, but resetting the Play Services proves it can't be the case.

[Bharani Cherukuri (Mobile Ads SDK Team)]

Hello Liran, 

Apologize for the confusion. From what I understand, you were receiving a no fill from the ad server before resetting the play services, and now it has been fixed. If that's the case, please note that, as you're able to load ads on all other devices except Nexus 5x, it points that this could be a device specific issue. Resetting Google play services would clear the cache and reset the device settings.

If you still have an issue with this, could you provide us the details about the device where the issue is reproducible along with the Ad Unit ID in question so we can take a look and assist you further. Additionally, if you could provide me the specific device logs when you're requesting the ads, it would be really helpful. 

Regards,

Bharani Cherukuri

Mobile Ads SDK Team

On Friday, October 13, 2017 at 7:16:31 AM UTC-4, Liran Barsisa wrote:

[Liran Barsisa]

I'm not receiving anymore. i received it over and over in the day I reported about it, and then I tried to reset the Play-Services, and then the issue was gone.

It was never fixed. 

If it was a device issue, resetting the Play-Services wouldn't have helped.

[Bharani Cherukuri (Mobile Ads SDK Team)]

Hello Liran, 

Thank you for the additional details. We would require the complete device logs from the console so we can take a look if the request and response events are triggered from the SDK. Can you elaborate on the steps performed to reset the Play-services?

Regards,

Bharani Cherukuri

Mobile Ads SDK Team

On Friday, October 13, 2017 at 7:16:31 AM UTC-4, Liran Barsisa wrote:

[Liran Barsisa]

In order to clear data of any app, you go to the app-info screen of it, and choose to clear it.

The same goes for the Play-Services app.

About logs, this was too long ago, and I think I've flashed Android 8.1 since then, which resets everything (sadly).

[Drew]

Incase anyone is reading this that had the same issue I had.... simply doing what Liran Barsisa said fixed it... delete google play services data and your app data. I had noticed an issue where I changed my package name and stopped getting ads served on one of my test devices. Simply deleting both data fixed it. THANK YOU. Days spent lost on this. 

[Diego Manhaes Amorim]

Hello. Drew, Liran Barsisa and all.  fixed the problem Here. Thanks