Hi Rogoon,
Thank you for reaching out to us.
Issues related to package names are usually caused by an improper Authorized Sellers for Apps (aka app-ads.txt) setup. Could you kindly confirm if your publisher ID is already whitelisted in your website's app-ads.txt file? You may check this page for further details on how to do this.
|
||||||
Hi Rogoon,
Thank you for updating us on your concern.
Could you kindly provide the details below (via Reply to author or a direct, private reply to this email) so that I can investigate the issue?
--
---
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/e3b26384-02d8-4224-972d-7774cd0b577co%40googlegroups.com.
Hi Rogoon,
Thank you for providing the requested details.
I was able to test your ad unit IDs with our sample app, and can confirm that I was receiving ads from them (see attached screenshots). With that said, I can also confirm that I get an error code 3 (No ad config) whenever I try using the package name you've provided.
Since you are using the Ad Manager alongside AdMob, you may want to check out this page for a primer on app-ads.txt within the context of Ad Manager as well. Kindly note that there may be additional steps (as labeled in that page) that you still need to do within your Ad Manager account in order to get the app-ads.txt feature fully functional.
Hi Amit,
Thank you for reaching out to us.
It seems that you have already created a thread and/or joined other threads regarding your own concern. Kindly continue on your own thread instead so that we can assist you better on it.
curl -iL -A "'Mozilla/5.0 (compatible; Googlebot/2.1; +http://www.google.com/bot.html).'" our-site.com/app-ads.txtWe ran through the other steps on this page and everything seems in order. We are also using Firebase in our project but haven't linked it with our ads account. Could that be the problem? Running out of ideas.

|
||||||
Hi Yunlong,
Thank you for reaching out to us.
That is entirely possible, yes, especially if your app (in the Play Store) links back to your website. You may want to check out this page for further details on how to resolve the same issue. Kindly note that you may have to wait at least 24 hours before your newly-created app-ads.txt file could be crawled and verified by Google.
|
||||||
|
||||||
--
---
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/d22e7771-2746-42af-9e1f-3e35daf761can%40googlegroups.com.
Hi Rogoon,
Thank you for updating us on your concern.
This sounds like it is related to the no ad config that you've been receiving lately. Could you kindly provide the details below (via Reply to author or a direct, private reply to this email) so that I can further investigate the issue?
|
||||||
Hi Mars,
Thank you for reaching out to us.
It seems that you've already created your own thread here. Let us continue there instead so that we can better assist you on your concern.
Hi Bryar,
Thank you for reaching out to us.
Kindly create a new thread if you have any concerns with the AdMob SDK.
Hi Yunlong,
Thank you for reaching out to us.
I would recommend reaching out to the Ad Manager Help Center for further assistance on your account-related concern, as I'm afraid that we can only assist you with your technical concerns on the AdMob SDK in this forum. You may also refer to this page to learn more about app-ads.txt, in context with the Ad Manager.
|
||||||
|
||||||
|
||||||
|
||||||
Hi there,
Thank you for reaching out to us.
Kindly create a new thread if you have any concerns with the AdMob SDK.
|
||||||