Android Question Can't show test ads...

[tufanv]

Hello,

I am having this trouble for some time and it is really getting harder to test ad implementations. What I get from the unfiltered logs are :

AD Error Code: 3
Use AdRequest.Builder.addTestDevice("1BF76F3B1F0A7BCAA2FE57E91364BE63") to get test ads on this device.
#007 Could not call remote method. @28
java.lang.NullPointerException: Attempt to invoke interface method 'java.lang.String com.google.android.gms.internal.ads.zzcyu.getVersion()' on a null object reference
    at com.google.android.gms.internal.ads.zzanl.getVersion(com.google.android.gms:play-services-ads-lite@@18.2.0:32)
    at com.google.android.gms.internal.ads.zzcql.zzamd(com.google.android.gms:play-services-ads@@18.2.0:10)
    at com.google.android.gms.internal.ads.zzcqo.call(com.google.android.gms:play-services-ads@@18.2.0)
    at com.google.android.gms.internal.ads.zzddz.zzapg(com.google.android.gms:play-services-ads@@18.2.0:5)
    at com.google.android.gms.internal.ads.zzddh.run(com.google.android.gms:play-services-ads@@18.2.0:8)
    at com.google.android.gms.internal.ads.zzddw.run(com.google.android.gms:play-services-ads@@18.2.0:8)
    at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1112)
    at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:587)
    at java.lang.Thread.run(Thread.java:818)
JobName = verial, Success = true
Not retrying to fetch app settings
Background sticky concurrent mark sweep GC freed 229915(12MB) AllocSpace objects, 20(719KB) LOS objects, 21% free, 29MB/37MB, paused 1.588ms total 110.437ms
Ad failed to load : 3

what may be the cause ? I have both tested on real device and emulator

 

[DonManfred]

what may be the cause ?

maybe the outdated artifact? Newest is 18.3.0

 

[tufanv]

maybe the outdated artifact? Newest is 18.3.0

Thanks for reply. I tried to update it with sdk manager but 18.3.0 also not working.

 

[tufanv]

My bad, It seems like the impression cap was blocking the ads.

 

[sorex]

yeah, it's silly that it reports no fill errors when using timers on the admob side instead of something more describing.

especially when testing things you constantly request ads but when you set a cap on 1/10 minutes you think it's bugging but it isn't.