Admob banner doesnt show up

2,226 views
Skip to first unread message

Jan Soukup

unread,
Oct 27, 2018, 6:14:22 PM10/27/18
to google-adm...@googlegroups.com
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)

Im using latest versions of firebase ads 17.0.0

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

Im trying out on other apps which shows ads banners, and its not showing either.

If you could help me a bit it would be great ;). Im getting a bit desperate.
Thank you, Jan

mobileadssdk-a...@google.com

unread,
Oct 29, 2018, 2:10:52 AM10/29/18
to Jan Soukup, Google Mobile Ads SDK Developers
Hi Jan,

Thank you for the error logs and other details provided.

It is logical that you thought about your WiFi connection, given that the Error Code 2 is primarily a Network Error.

That said, since you are able to load ads in an emulator and another Android device, then it's safe to assume that your code implementation is working. There might be an issue specific to the network you are connected to or the Samsung Galaxy S7 device you are testing on.

For us to narrow down the root cause of the Network Error you encountered, could you provide to us the following information?
  • Is your Samsung Galaxy S3 device (where test ads are loading) connected to the same WiFi network your Samsung Galaxy S7 device (where test ads are not loading) is connected to?
  • Could you run our sample app in your Samsung Galaxy S7 device in the same WiFi network and see if you get the same Error Code 2?
  • Could you capture a Network Tracing logs when you encounter the Error Code 2 in your Samsung Galaxy S7 device?
Regards,
Ivan Bautista
Mobile Ads SDK Team




On 10/28/18 06:14:22 jan.s...@gmail.com wrote:
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.

cnd

unread,
Nov 2, 2018, 2:17:58 AM11/2/18
to Google Mobile Ads SDK Developers
Getting same issues in my oneplus 5 (Android 8+) device. No issues in old Nexus 5(Android 6) device.

mobileadssdk-a...@google.com

unread,
Nov 5, 2018, 4:50:34 PM11/5/18
to cnd, Google Mobile Ads SDK Developers
Hi there,

It sounds like a device specific issue and we would suggest that you reset the device and try again and see if you are still seeing the errors.

Regards,
Deepika Uragayala
Mobile Ads SDK Team
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
Also find us on our blog and Google+ page:
    http://googleadsdeveloper.blogspot.com
    https://plus.google.com/115658573333388777174/
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~

--

---
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.

Stephen Borden

unread,
Feb 28, 2020, 10:31:27 AM2/28/20
to Google Mobile Ads SDK Developers
I'm also seeing this issue, banner ads are not showing on a Samsung Galaxy Tab on Android 8, but appear on other devices. Was anyone here able to find a solution?

Mobile Ads SDK Forum Advisor Prod

unread,
Feb 28, 2020, 3:18:10 PM2/28/20
to skate...@gmail.com, google-adm...@googlegroups.com
Hello Stephen,

Did you try to reset the device or tried on any other  Samsung Galaxy Tab? Are you seeing any error code in the logs when the Ad request was failed? Please share the complete device logs and the Ad unit Id so that we can try to get hold of a device and try on our end as well. You can use "Reply Privately to Author" option to share the details privately. 


Regards,
Deepika Uragayala
Mobile Ads SDK Team
 

ref:_00D1U1174p._5001UXTYRP:ref

Mobile Ads SDK Forum Advisor Prod

unread,
Mar 2, 2020, 12:34:05 AM3/2/20
to skate...@gmail.com, google-adm...@googlegroups.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

ad_banner_tablet.png
Reply all
Reply to author
Forward
0 new messages