Android 1.5 emulator shows no ads on SDK v4.0.4
292 views
Skip to first unread message
Justin
Apr 13, 2011, 4:11:09 PM4/13/11
to Google AdMob Ads Developers
I started my app up in an Android 1.5 emulator using the 4.0.4 SDK
implemented with the XML layout option documented here
http://code.google.com/mobile/ads/docs/android/banner_xml.html. I
turned testing mode on in the AdRequest. When I load the app, no ads
show. I can see in the logcat that it attempts to pull an ad, but
eventually returns the following:
04-13 15:10:03.656: INFO/Ads(698): AdLoader timed out while getting
the HTML.
04-13 15:10:03.667: INFO/Ads(698): onFailedToReceiveAd(A network error
occurred.)
Keep in mind that this exact same code base will produce an ad on a
1.6+ emulator. The above errors are the only differences in the
output.
implemented with the XML layout option documented here
http://code.google.com/mobile/ads/docs/android/banner_xml.html. I
turned testing mode on in the AdRequest. When I load the app, no ads
show. I can see in the logcat that it attempts to pull an ad, but
eventually returns the following:
04-13 15:10:03.656: INFO/Ads(698): AdLoader timed out while getting
the HTML.
04-13 15:10:03.667: INFO/Ads(698): onFailedToReceiveAd(A network error
occurred.)
Keep in mind that this exact same code base will produce an ad on a
1.6+ emulator. The above errors are the only differences in the
output.
Sven
Apr 15, 2011, 2:03:09 PM4/15/11
to Google AdMob Ads Developers
I have the same problem. It also completely blocks any AsyncTasks
while futilely trying to download the ad for ~30 seconds.
On Apr 14, 6:11 am, Justin <jtgi...@gmail.com> wrote:
> I started my app up in an Android 1.5 emulator using the 4.0.4 SDK
> implemented with the XML layout option documented herehttp://code.google.com/mobile/ads/docs/android/banner_xml.html. I
while futilely trying to download the ad for ~30 seconds.
On Apr 14, 6:11 am, Justin <jtgi...@gmail.com> wrote:
> I started my app up in an Android 1.5 emulator using the 4.0.4 SDK
Michael Diener
Apr 21, 2011, 11:40:16 AM4/21/11
to Google AdMob Ads Developers
I'm also experiencing this using AdWhirl 3.0.0 and SDK 4.0.4. Changing
the default log level of "Ads" brought some more information. Looks
like loading the ad is blocked until the timeout. Wes or anybody else
from Google/Admob, could you please have a look?
I have shortened the log to take out any IDs - if you need the full
log, just send me an email.
/Michael
04-21 15:23:27.634: VERBOSE/Ads(768): Ad request started.
04-21 15:23:27.694: INFO/Ads(768): adRequestUrlHtml:
<html><head><script src="http://www.gstatic.com/afma/sdk-core-
v40.js"></script><script>AFMA_buildAdURL({"msid":"xxx","simulator":
1,"hl":"en","preqs":4,"u_so":"p","slotname":"xxx","js":"afma-sdk-a-
v4.0.4","app_name":"4.0.4.android.xxx","isu":xxx","u_audio":4,"u_w":
320,"testing":1,"cap":"a","format":"320x50_mb","u_sd":
1.0,"net":"ed","u_h":480});</script></head><body></body></html>
04-21 15:23:29.174: DEBUG/Ads(768): shouldOverrideUrlLoading("gmsg://
mobileads.google.com/loadAdURL?type=admob&...")
04-21 15:23:29.224: INFO/Ads(768): Received ad url: <"url": "http://
r.admob.com:80/ad_source.php?
msidxxx&hl=en&preqs=4&u_so=p&slotname=xxx&js=afma-sdk-a-
v4.0.4&app_name=4.0.4.android.xxx&isu=xxx&u_audio=4&u_w=320&cap=a&format=320x50_mb&u_sd=1&net=ed&u_h=480&adtest=on&test_action=overlay&output=html®ion=mobile_app&u_tz=0&ex=1&client_sdk=1&askip=4",
"afmaNotifyDt": "null">
04-21 15:24:27.733: INFO/Ads(768): AdLoader timed out while getting
the HTML.
04-21 15:24:27.864: INFO/Ads(768): onFailedToReceiveAd(A network error
occurred.)
04-21 15:24:28.513: DEBUG/Ads(768): Response content is: <!doctype
html>
04-21 15:24:28.513: DEBUG/Ads(768): <html>
...
04-21 15:24:28.513: DEBUG/Ads(768): </html>
04-21 15:24:28.573: VERBOSE/Ads(768): Ad request started.
the default log level of "Ads" brought some more information. Looks
like loading the ad is blocked until the timeout. Wes or anybody else
from Google/Admob, could you please have a look?
I have shortened the log to take out any IDs - if you need the full
log, just send me an email.
/Michael
04-21 15:23:27.634: VERBOSE/Ads(768): Ad request started.
04-21 15:23:27.694: INFO/Ads(768): adRequestUrlHtml:
<html><head><script src="http://www.gstatic.com/afma/sdk-core-
v40.js"></script><script>AFMA_buildAdURL({"msid":"xxx","simulator":
1,"hl":"en","preqs":4,"u_so":"p","slotname":"xxx","js":"afma-sdk-a-
v4.0.4","app_name":"4.0.4.android.xxx","isu":xxx","u_audio":4,"u_w":
320,"testing":1,"cap":"a","format":"320x50_mb","u_sd":
1.0,"net":"ed","u_h":480});</script></head><body></body></html>
04-21 15:23:29.174: DEBUG/Ads(768): shouldOverrideUrlLoading("gmsg://
mobileads.google.com/loadAdURL?type=admob&...")
04-21 15:23:29.224: INFO/Ads(768): Received ad url: <"url": "http://
r.admob.com:80/ad_source.php?
msidxxx&hl=en&preqs=4&u_so=p&slotname=xxx&js=afma-sdk-a-
v4.0.4&app_name=4.0.4.android.xxx&isu=xxx&u_audio=4&u_w=320&cap=a&format=320x50_mb&u_sd=1&net=ed&u_h=480&adtest=on&test_action=overlay&output=html®ion=mobile_app&u_tz=0&ex=1&client_sdk=1&askip=4",
"afmaNotifyDt": "null">
04-21 15:24:27.733: INFO/Ads(768): AdLoader timed out while getting
the HTML.
04-21 15:24:27.864: INFO/Ads(768): onFailedToReceiveAd(A network error
occurred.)
04-21 15:24:28.513: DEBUG/Ads(768): Response content is: <!doctype
html>
04-21 15:24:28.513: DEBUG/Ads(768): <html>
...
04-21 15:24:28.513: DEBUG/Ads(768): </html>
04-21 15:24:28.573: VERBOSE/Ads(768): Ad request started.
kunal0072005
Apr 21, 2011, 11:56:34 AM4/21/11
to google-adm...@googlegroups.com
Well Actually it is speciffying with u the correct erroe i.e. (A network error occured),
Its not able to send request due to not working internet on the emulator, have you all checked that
if in your browser the Google page or aany webpage is opening,
Also have you checked it on a real device,
Also it will show the same for all android version's emulator, i think it isnt the problem of version of android...
Pls do check if webpage is opening on your emulators
Michael Diener
Apr 21, 2011, 2:44:42 PM4/21/11
to Google AdMob Ads Developers
No, it is not the correct error. After the timeout you see that the ad
is loaded. And yes, of course there is network connectivity...
So again, this issue only happens on 1.5 as the other guys mentioned
as well. My guess is, that is connected to some WebView/WebViewClient
behavior that is different from the other Android versions. Without
the source of the Google AdMob SDK it is hard to debug, but I hope the
extended log helps somebody at Google to look into this.
/Michael
is loaded. And yes, of course there is network connectivity...
So again, this issue only happens on 1.5 as the other guys mentioned
as well. My guess is, that is connected to some WebView/WebViewClient
behavior that is different from the other Android versions. Without
the source of the Google AdMob SDK it is hard to debug, but I hope the
extended log helps somebody at Google to look into this.
/Michael
wes
Apr 21, 2011, 4:49:51 PM4/21/11
to google-adm...@googlegroups.com
That seems weird. I even bumped up the timeout value to 4 minutes and it still failed to retrieve an ad on the 1.5 emulator. I'll do some more checking and let you know what I find.
Cheers,
Wes
Justin Giles
Apr 21, 2011, 4:51:10 PM4/21/11
to google-adm...@googlegroups.com
Just a FYI...this is even true on a 1.5 device.
wes
Apr 21, 2011, 8:48:47 PM4/21/11
to google-adm...@googlegroups.com
Bah, it's an issue with the AsyncTask pool size on Android 1.5 (which is...1). We'll see what we can do.
Cheers,
Wes
Michael Diener
May 15, 2011, 4:10:34 AM5/15/11
to Google AdMob Ads Developers
I just downloaded the AdMob SDK again to see if there is an update to
4.0.4 and I was lucky to see 4.1.0. Maybe it would be useful for
everybody if you announce new releases here in this group.
I noted, that the SDK requires now Android 1.6 (in contrast to 4.0.4
that required 1.5) so I assume there is no fix to the problem of this
thread.
One more thing, I did not find any release notes and would appreciate
if the change log would be available somewhere to see which things got
fixed. If there is a website with this information I would appreciate
if somebody could point me to it - I didn't find anything.
Regards,
Michael
On Apr 22, 2:48 am, wes <wesgood...@google.com> wrote:
> Bah, it's an issue with the AsyncTask pool size on Android 1.5 (which
> is...1). We'll see what we can do.
>
> Cheers,
> Wes
>
>
>
>
>
>
>
> On Thu, Apr 21, 2011 at 1:51 PM, Justin Giles <jtgi...@gmail.com> wrote:
> > Just a FYI...this is even true on a 1.5 device.
>
4.0.4 and I was lucky to see 4.1.0. Maybe it would be useful for
everybody if you announce new releases here in this group.
I noted, that the SDK requires now Android 1.6 (in contrast to 4.0.4
that required 1.5) so I assume there is no fix to the problem of this
thread.
One more thing, I did not find any release notes and would appreciate
if the change log would be available somewhere to see which things got
fixed. If there is a website with this information I would appreciate
if somebody could point me to it - I didn't find anything.
Regards,
Michael
On Apr 22, 2:48 am, wes <wesgood...@google.com> wrote:
> Bah, it's an issue with the AsyncTask pool size on Android 1.5 (which
> is...1). We'll see what we can do.
>
> Cheers,
> Wes
>
>
>
>
>
>
>
> On Thu, Apr 21, 2011 at 1:51 PM, Justin Giles <jtgi...@gmail.com> wrote:
> > Just a FYI...this is even true on a 1.5 device.
>
> > On Thu, Apr 21, 2011 at 3:49 PM, wes <wesgood...@google.com> wrote:
>
> >> That seems weird. I even bumped up the timeout value to 4 minutes and it
> >> still failed to retrieve an ad on the 1.5 emulator. I'll do some more
> >> checking and let you know what I find.
>
> >> Cheers,
> >> Wes
>
>
> >> That seems weird. I even bumped up the timeout value to 4 minutes and it
> >> still failed to retrieve an ad on the 1.5 emulator. I'll do some more
> >> checking and let you know what I find.
>
> >> Cheers,
> >> Wes
>
Reply all
Reply to author
Forward
0 new messages