Why am I seeing Error Code 3: No Ad Config on Android?

[Rogoon]

Hello everyone,

Was directed here from the Ads Manager forums. Looking for some advice on an issue we've been facing.

We have ads setup for both our iOS and Android apps. Last month our ad impressions dropped off on Sep 14th for our Android build. We had recently set up a new unit ID, however, it was loading ads correctly for both apps before the 14th. Now when testing I get the following error when requesting an ad:

​E/ads: {

      "Code": 3,

      "Message": "No ad config.",

      "Domain": "com.google.android.gms.ads",

      "Cause": "null",

      "Response Info": {

        "Response ID": "null",

        "Mediation Adapter Class Name": "",

        "Adapter Responses": []

      }

    }

I thought this was a no fill error but the "no ad config" message makes me think its something else?

I tried the new unit ID on a sample app and ads loaded correctly. I then tried changing the package name of our Android build and ads also loaded fine with the unit ID. I'm not sure why just our package name would be causing issues with ads loading.

Any advice would be appreciated.

Thank you!

[Ad Manager API Forum Advisor Prod]

Hi there,

 

This looks more like a Mobile Ads SDK concern rather than an Ad Manager API concern. Please reach out to their team in this link for better assistance.

 

Regards,

Kevin Gil Soriano Ad Manager API Team

ref:_00D1U1174p._5004Q267n5K:ref