Google Ad Manager Ads (Test & Real) not loading

[Alap Patel]

I've recently changed my lost app signing key via Google Play Console (through Play Console App Integrity support) and it was successful. Now, I can upload my app having the same package id by signing with the newly updated key.

But after this change, Google Ad Manager tests Ads using Test Ad Units("/6499/example/banner") and real ads both are not loading and showing errors in logcat like "Error 3: Ad failed to load".

What I've already tested but didn't work:

• Tried to load the test ads using test ad units. (/6499/example/banner)
• Tried to load test ads by adding test devices as suggested in the logcat.
• Added app-ads.txt for testing as well.
• The same code implementation works perfectly in other apps
• The same code implementation works perfectly if I change the package id. (For eg: "com.world.news.alap" to "com.worldwide.news.alap".
  

Please help me to solve the issue.

My App Link: https://play.google.com/store/apps/details?id=com.world.news.alap

[Mobile Ads SDK Forum Advisor]

Hi Alap,

Thank you for reaching out to us.

Could you confirm if you added the following (google.com, pub-3940256099942544, DIRECT, f08c47fec0942fa0) in your your app-ads.txt file as this is needed in order to receive test ads from our demo units. Since you mentioned that this is only happening to a specific package id, it looks like this has something to do with your package id. With that, we recommend reaching out to the Product Support Team to assist you better on this. 

Regards,

Princess Pamela Mobile Ads SDK Team

 

ref:_00D1U1174p._5004Q2dJTd4:ref

[Alap Patel]

Yes. I've added the mentioned app-ads.txt content for test ads as well.

And yes, the issue is only with the package id: "com.world.news.alap" for which I've recently changed the app signing key in the Google Play Console because I've lost the key. Does this chage affect the ad serving? As it changes the SHA certificate which is used in the Firebase previously.

[Mobile Ads SDK Forum Advisor]

Hi Alap,

I work along with Princess Pamela. Allow me to assist you in this.

To give you more context, if your app is new and under review, the app will experience limited ad serving. Reviews will typically take 24-48 hours, but may take longer in certain cases. As per your use case, since you mentioned that you have changes specially with the app signing, then it could be the reason why ads is not servings as it is treated as new app. However, our team cannot validate this as ad serving issues is out of our expertise. With this, we would highly recommend raising this to the Product Support Team instead as they are more equipped in handling such concerns.

Regards,

Teejay Wennie Mobile Ads SDK Team

ref:_00D1U1174p._5004Q2dJTd4:ref

[Alap Patel]

Hi Teejay,

I've raised the same issue with the Product Support Team but haven't received any response yet. It would be nice if you look into it from your end. My app can't even load Admob or Google AD Manager test ads using test ad units or testing devices. Let me know if you have any solution for loading at-least test ads. So, this is not a case of review or approval because at least test ads should load. But while loading test ads, it also gives an "Ad Failed To Load 3" error message.

[Mobile Ads SDK Forum Advisor]

Hi Alap,

Some publisher's also encounter this behavior wherein they can't load any test ads as well. What we suggest is to use our demo app ID ca-app-pub-3940256099942544~3347511713. Could you try it on your end, then let me know how it goes?

[Alap Patel]

Nothing works. Every time it just shows "Ad failed to load 3", "No ad config". I've tried to load both Admob and AdManager Test Ads but doesn't work.

The issue is with the Package Id: com.world.news.alap

If I change the package name like com.worldwide.news.alap, then everything works perfectly fine. Please help. Why are Ads not loading only for a specific package id?

[Mobile Ads SDK Forum Advisor]

Hi Alap,

Since everything is not working in your end and you already reached out to the product support team, can you provide us privately your app id and app-ads.txt file via Reply privately to author option or directly provide it to the link below?

If the file(s) you are looking to share are less than 25mb in total you can attach them to this case on your next reply. If you are having trouble attaching your file to this case or if your file(s) are larger than 25mb, you can share your files with me by performing the following steps:

1. Navigate to https://docs.google.com/forms/d/e/1FAIpQLSfkAiXMeYP-fw1W3Z-tT9uwmATEKO5X6S-th0gR2ezdKaaqfg/viewform?usp=pp_url&entry.400550049=Mobile+Ads+SDK&entry.460850823=5004Q00002dJTd4QAG&entry.80707362=00116884
2. Fill out all fields, and attach your file(s).
3. Please reply back on this thread when you have uploaded your file(s). Please do not share this link.

Regards,

Princess Pamela Mobile Ads SDK Team

ref:_00D1U1174p._5004Q2dJTd4:ref

[Alap Patel]

Any feedback received from the team? Any update on the issue?

[Mobile Ads SDK Forum Advisor]

Hi Alap,

Thank you for providing that information. Could you please send over a Charles log of the ad request so we can further diagnose the issue? 

Thanks,
Justin

 

ref:_00D1U1174p._5004Q2dJTd4:ref

[Alap Patel]

Sorry, but I don't know about Charles's log and I don't want to do that. Can't you simply connect with the Google Admob/Ad Manager team and resolve the package id-specific ads not showing issue?

[Alap Patel]

Any update on the issue?

[JBarbosa]

hello, guys, I'm having exactly the same problem, in the original package I get error 3 in the ad config, changing it works, follow charles' log to see if it helps

[Alap Patel]

Thank you for sharing the Charles log.

Hope, Google Support team now resolve the issue. Please provide the update.

--

---
You received this message because you are subscribed to a topic in the Google Groups "Google Mobile Ads SDK Developers" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/google-admob-ads-sdk/qOzfRumV3So/unsubscribe.
To unsubscribe from this group and all its topics, send an email to google-admob-ads...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-admob-ads-sdk/a2643f56-7905-4818-9c9a-2e4b52192245n%40googlegroups.com.

[Mobile Ads SDK Forum Advisor]

Hello,

Thank you for flagging this as well. Can you please include the ad request in the Charles log? 

For ad manager it will be

https://pubads.g.doubleclick.net/gampad/ads?...

For admob it will be

https://googleads.g.doubleclick.net/mads/gma?...

[JBarbosa]

I'm not getting it, I installed the certificate but it doesn't work for this url

[Mobile Ads SDK Forum Advisor]

Hello,

I recommend troubleshooting the error message you are seeing in the Charles log. To be sure everything is working as it should, follow steps that are outlined here. To proceed any further we will need to see an ad request and response in the logs. 

[JBarbosa]

thanks for the help, I was missing enabling the ads debug, now I got it

[Mobile Ads SDK Forum Advisor]

Hello,

Thank you for providing the log with the request. Could you test with your own app and ad unit ID? Then enable test ads. Please provide the Charles log as well. 

My current suspicion is the app ID and ad unit ID don't match, so causing no ad to return.

[Alap Patel]

Hi JBarbosa,

Did you find the solution of Ads not loading error code 3? Are you able to show test ads or live ads?

--

---
You received this message because you are subscribed to a topic in the Google Groups "Google Mobile Ads SDK Developers" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/google-admob-ads-sdk/qOzfRumV3So/unsubscribe.
To unsubscribe from this group and all its topics, send an email to google-admob-ads...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/google-admob-ads-sdk/a9a82b17-8259-4580-8d14-2f743b64b3ccn%40googlegroups.com.

[Luitgardus Say]

https://youtu.be/606j6_iJVa4

You received this message because you are subscribed to the Google Groups "Google Mobile Ads SDK Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-admob-ads...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-admob-ads-sdk/CABbuZzBaC54TQH6jiNA2wpSabR8mVCxjJsSfuUG7F73_sfTX8A%40mail.gmail.com.

[JBarbosa]

Now with all the production ids (ad manager), as we know it gives the same result as using the test one

[Mobile Ads SDK Forum Advisor]

Hello,

Thank you for providing that. I have forwarded your issue to Ad Manager serving team with the information provided and will have an update for you as soon as we can. 

[JBarbosa]

I tried with admob too, the result is the same

[Alap Patel]

Same for me as well. Tried both Admob and Admanager but only receiving error code 3 even for test ads as well.

--

---
You received this message because you are subscribed to a topic in the Google Groups "Google Mobile Ads SDK Developers" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/google-admob-ads-sdk/qOzfRumV3So/unsubscribe.
To unsubscribe from this group and all its topics, send an email to google-admob-ads...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/google-admob-ads-sdk/2f58f6db-33ec-4c26-90e1-407cfc9f2b36n%40googlegroups.com.

[Mobile Ads SDK Forum Advisor]

Hello,


If you're seeing ads serve by changing the package ID of your app, but not with your app's main package name, it almost always means one of two things:

- Your app-ads.txt isn't configured properly
- Your app has been flagged for some policy-related issue, either ads policy or Play policy (the latter would stop ad serving)

@JBarbosa I was able to find the app package from your Charles log and confirm that your app-ads.txt looks correct, so in your case I strongly suspect it's the second case.

On this forum, we are only equipped to debug SDK integration issues. For more information about potential policy issues, check the Policy center to try and self-diagnose, or contact Product support.

Thanks,
Eric, Mobile Ads SDK Team 

ref:_00D1U1174p._5004Q2dJTd4:ref