I'm trying to setup AdMob in my Android application and everything was working great until I tried it out on live devices. On all testing everything worked fine but after building for release and testing on some real devices I can't seem to get any ads to display.
In the logcat I see the following:
11-24 21:54:31.170: W/Ads(16897): JS: The page displayed insecure content!
11-24 21:54:31.170: W/Ads(16897): (null:1)
11-24 21:54:31.180: W/Ads(16897): JS: The page displayed insecure content!
11-24 21:54:31.180: W/Ads(16897): (null:1)
11-24 21:54:31.185: W/Ads(16897): JS: The page displayed insecure content!
11-24 21:54:31.185: W/Ads(16897): (null:1)
11-24 21:54:31.425: W/Ads(16897): Received error HTTP response code: 400
11-24 21:54:31.425: W/Ads(16201): There was a problem getting an ad response. ErrorCode: 0
11-24 21:54:31.455: W/Ads(16201): Failed to load ad: 0
--
---
You received this message because you are subscribed to a topic in the Google Groups "Google AdMob Ads Developers" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/google-admob-ads-sdk/ETa57Wld2_4/unsubscribe.
To unsubscribe from this group and all its topics, send an email to google-admob-ads...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
2014-11-25 19:29 GMT+01:00 Andrew Brogdon (Mobile Ads SDK Team) <mobileadssdk-advisor+andrew@google.com>:
AdMob is moving toward serving ad responses via HTTPS, which sometimes causes messages like the first six lines of your log (if any of the ad's images/css/etc. are served over HTTP instead, it produces a warning). This normally doesn't interfere with loading the ad, though, which you're also seeing.If you replace the Ad Unit ID you're using with a test Ad Unit ID (you can get one from our Quick Start), and compile a release for your test devices, do you still end up with Error Code 0?-Andrew
On Tuesday, November 25, 2014 6:33:23 AM UTC-8, Licari Work wrote:I'm trying to setup AdMob in my Android application and everything was working great until I tried it out on live devices. On all testing everything worked fine but after building for release and testing on some real devices I can't seem to get any ads to display.
In the logcat I see the following:
11-24 21:54:31.170: W/Ads(16897): JS: The page displayed insecure content! 11-24 21:54:31.170: W/Ads(16897): (null:1) 11-24 21:54:31.180: W/Ads(16897): JS: The page displayed insecure content! 11-24 21:54:31.180: W/Ads(16897): (null:1) 11-24 21:54:31.185: W/Ads(16897): JS: The page displayed insecure content! 11-24 21:54:31.185: W/Ads(16897): (null:1) 11-24 21:54:31.425: W/Ads(16897): Received error HTTP response code: 400 11-24 21:54:31.425: W/Ads(16201): There was a problem getting an ad response. ErrorCode: 0 11-24 21:54:31.455: W/Ads(16201): Failed to load ad: 0
--
---
You received this message because you are subscribed to a topic in the Google Groups "Google AdMob Ads Developers" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/google-admob-ads-sdk/ETa57Wld2_4/unsubscribe.
To unsubscribe from this group and all its topics, send an email to google-admob-ads-sdk+unsub...@googlegroups.com.
02-19 21:21:02.080: W/Ads(24069): JS: The page athttps://googleads.g.doubleclick.net/mads/static/mad/sdk/native/sdk-core-v40.html displayed insecure content from file:///android_asset/webkit/android-weberror.png.
Also