GoogleMobileAds-v6.1.0 don't show Test Ads using test ad units

[AllanRW]

Latest release don't show test ads using the test ad units from the docs, only way to show test ads is to add device to Admob console as a test device. I prefer to use test ad units, is this feature removed or its a bug?

[Marounkattar]

the same problem can we know why?

[lazycoder71]

I got the same problem, the interstitial OnLoadFailed call back return this: { "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": [] }

[arksh1]

i got the same problem. my plugin version is 6.0.1. last month, it' ok. but now, i got problem. (same build)

[horoeil]

I have the same problem. QQ

Unity 2021.1.20f1 plugin version is 6.1.0

[Cptweirdo]

Same problem

Unity 2018.4.26f1 plugin v6.1.0

[AiMAnsarie]

Same problem

Unity 2020.3.10f1 Plug-in v6.1.0

[Mecze]

+1 Same problem here

[Mecze]

On one of our older projects with Admob plugin 4.2.1 it does have the same problem.

[Mecze]

Any new on this? we still receiving no test ads Anyone found a workaround?

[ghost]

The only approach currently working is using real ads with test devices

[bfaf]

Same problem with:

Unity 2021.1.22 GoogleMobileAds-v6.1.1

[desouse]

It works for me - https://developers.google.com/admob/android/test-ads#demo_ad_units

[RicardoGuzmanVelasco]

Same, also with AdMob 6.0.1, Unity 2020.3.19 LTS. Neither working upgrading to AdMob 6.1.1. Have tried any permutation, it drove us nuts! At first we thought it was a problem on our side after some API changes — both setting the builder up as test device when using a testing ID as well:

Removed Birthday, Gender, TestDevices, TagForChildDirectedTreatment properties on AdRequest. TagForChildDirectedTreatment and TestDeviceIds properties are available under RequestConfiguration.

Thus we tried not-testing device with testing ID, testing device with testing ID, none of them, and so forth. Any testing ad returns "no ad config" aforementioned. Herewith I repeat it:

{
      "Response Info": {
        "Adapter Responses": [],
        "Mediation Adapter Class Name": "",
        "Response ID": "null"
      },
      "Domain": "com.google.android.gms.ads",
      "Message": "No ad config.",
      "Code": 3,
      "Cause": "null"
    }

[RicardoGuzmanVelasco]

Fixed it

It works for me - https://developers.google.com/admob/android/test-ads#demo_ad_units

Fixed it the same way!

[khalidhex]

Christ ! does anybody found a workaround ?

[kim-young-min]

You can also test with AD Manager test ad units

https://developers.google.com/ad-manager/mobile-ads-sdk/android/test-ads

[princetongirl818]

Fixed it

It works for me - https://developers.google.com/admob/android/test-ads#demo_ad_units

Fixed it the same way!

how did you guys fix it? @RicardoGuzmanVelasco @kim-young-min @desouse

[desouse]

Hello @princetongirl818. All you need to do is just to add this to your app-ads.txt file in order for test ads to work: google.com, pub-3940256099942544, DIRECT, f08c47fec0942fa0 This is an instruction for adding the file app-ads.txt: https://support.google.com/admob/answer/9363762?hl=en

[kunny]

Since there were no recent activities for this issue, we are therefore reluctantly going to close this bug for now.

If you are still experiencing the problem, please file a new issue with the same description, what happens and system / network tracing / Charles logs.

All system setups can be slightly different, so it's always better to open new issues and reference the related ones. Thanks for your contribution.