Hi,I am requesting test ad in my app.When i start it in emulator, test ad shows up.When i start it on my older samsung galaxy s3, testad shows up.When i start it on my samsung galaxy s7, i got error ad load falied, error 2 (im online on wifi, i have a lot of space in storage)
2018-10-28 00:10:34.210 23513-23513/com.jenda.baseballboard I/Ads: This request is sent from a test device.
2018-10-28 00:10:34.242 23513-23513/com.jenda.baseballboard I/DynamiteModule: Considering local module com.google.android.gms.ads.dynamite:0 and remote module com.google.android.gms.ads.dynamite:320
2018-10-28 00:10:34.242 23513-23513/com.jenda.baseballboard I/DynamiteModule: Selected remote version of com.google.android.gms.ads.dynamite, version >= 320
2018-10-28 00:10:34.273 4834-8656/? D/AudioService: GetAppDevice, uid=10274
2018-10-28 00:10:34.275 4834-8656/? D/AudioService: getStreamVolume 3 index 0
2018-10-28 00:10:34.278 4834-8656/? D/AudioService: getStreamVolume 2 index 110
2018-10-28 00:10:34.310 4834-8656/? D/ConnectivityService: filterNetworkStateForUid() uid: 10274 networkInfo: [type: WIFI[] - WIFI, state: CONNECTED/CONNECTED, reason: (unspecified), extra: "dan", failover: false, available: true, roaming: false, metered: false]
2018-10-28 00:10:34.338 23513-23513/com.jenda.baseballboard I/DynamiteModule: Considering local module com.google.android.gms.ads.dynamite:0 and remote module com.google.android.gms.ads.dynamite:320
2018-10-28 00:10:34.338 23513-23513/com.jenda.baseballboard I/DynamiteModule: Selected remote version of com.google.android.gms.ads.dynamite, version >= 320
2018-10-28 00:10:34.352 23513-23513/com.jenda.baseballboard I/Ads: Ad failed to load : 2
If you could help me a bit it would be great ;). Im getting a bit desperate.Thank you, Jan
--
---
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-sdk+unsub...@googlegroups.com.
To post to this group, send email to google-admob-ads-sdk@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-admob-ads-sdk/10cebc74-8bec-4ad0-8d13-485040e11f4b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
--
---
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-sdk+unsub...@googlegroups.com.
To post to this group, send email to google-admob-ads-sdk@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-admob-ads-sdk/800dbfa2-2946-44ad-8816-a1fcd6ffd302%40googlegroups.com.
Hi Stephen,
Thank you for providing additional details on your concern.
I can confirm that the banner ad should be displaying properly on your end, as per the provided Logcat and Charles log. I was also getting an error code 3 message upon testing the ad unit ID with our sample app, using both a Google Pixel 3 XL (phone) and a Samsung Galaxy Tab A (tablet) as test devices. However, I was able to successfully display the banner ad from the Charles log after routing it to our internal testing systems (see attached screenshot).
With this in mind, it seems that this is more of an ad creative issue rather than an implementation one. I would recommend forwarding this concern over at the Ad Manager Help Center for further assistance on this matter. The product specialists there should be able to provide more insights on this.
Regards,
Ziv Yves Sanchez