Timed out waiting for adapter on nexus 4

540 views
Skip to first unread message

Giuseppe Iuculano

unread,
Jan 17, 2014, 3:41:21 AM1/17/14
to google-adm...@googlegroups.com
HI,

I use admob mediation (with Google Play services library) and from about a week I've a strange problem on Nexus 4, or at least I tried on a lot of phones and it is only on Nexus 4.

I tried with five Nexus 4, and 4 of 5 have this issue: ads are not shown with the following timeout error



I/Ads     ( 5474): Starting ad request.
I/Ads     ( 5474): Trying mediation network: 18351550913290782395
I/Ads     ( 5474): Timed out waiting for adapter.
I/Ads     ( 5474): No fill from any mediation ad networks.
I/Ads     ( 5474): Scheduling ad refresh 30000 milliseconds from now.
W/Ads     ( 5474): Failed to load ad: 3
I/Ads     ( 5474): Ad is not visible. Not refreshing ad.
I/Ads     ( 5474): Scheduling ad refresh 60000 milliseconds from now.
I/Ads     ( 5474): Timed out waiting for adapter.
I/Ads     ( 5474): Trying mediation network: 7681903010231960328
I/Ads     ( 5474): Instantiating mediation adapter: com.google.ads.mediation.inmobi.InMobiAdapter
D/dalvikvm( 1075): GC_CONCURRENT freed 613K, 22% free 10918K/13980K, paused 2ms+2ms, total 31ms
D/dalvikvm( 1075): WAIT_FOR_CONCURRENT_GC blocked 18ms
I/Ads     ( 5474): Timed out waiting for adapter.
I/Ads     ( 5474): Trying mediation network: 7681903010231960328
I/Ads     ( 5474): Instantiating mediation adapter: com.google.ads.mediation.inmobi.InMobiAdapter
I/Metrics:BatchTransmitte( 4847): QueuePusher.sendBatches - Drained batch queue.; Number of batches sent: 0
I/Ads     ( 5474): Timed out waiting for adapter.
I/Ads     ( 5474): Trying mediation network: 9372067028804390441
I/Ads     ( 5474): Instantiating mediation adapter: com.mdotm.android.admobadapter.MdotMAdapter
I/Ads     ( 5474): Trying mediation network: 5450213213286189855
I/Ads     ( 5474): Instantiating mediation adapter: com.google.ads.mediation.admob.AdMobAdapter
D/dalvikvm( 1075): GC_CONCURRENT freed 637K, 22% free 10905K/13980K, paused 2ms+2ms, total 52ms
I/Ads     ( 5474): Timed out waiting for adapter.
I/Ads     ( 5474): Trying mediation network: 9372067028804390441
I/Ads     ( 5474): Instantiating mediation adapter: com.mdotm.android.admobadapter.MdotMAdapter
I/Ads     ( 5474): Trying mediation network: 5450213213286189855
I/Ads     ( 5474): Instantiating mediation adapter: com.google.ads.mediation.admob.AdMobAdapter
I/Ads     ( 5474): Timed out waiting for adapter.
I/Ads     ( 5474): Trying mediation network: 18351550913290782395
I/Ads     ( 5474): Instantiating mediation adapter: com.google.ads.mediation.customevent.CustomEventAdapter
I/Ads     ( 5474): Timed out waiting for adapter.
I/Ads     ( 5474): Trying mediation network: 18351550913290782395
I/Ads     ( 5474): Instantiating mediation adapter: com.google.ads.mediation.customevent.CustomEventAdapter
I/Ads     ( 5474): Ad is not visible. Not refreshing ad.
I/Ads     ( 5474): Scheduling ad refresh 60000 milliseconds from now.

What is wrong?


Cheers,
Giuseppe


Eddie Lee

unread,
Jan 17, 2014, 7:38:22 AM1/17/14
to google-adm...@googlegroups.com
I've got the same problem. What's wrong with the admob google play services library?

Regards,
Eddie


2014/1/17 Giuseppe Iuculano <gius...@iuculano.it>

--
 
---
You received this message because you are subscribed to the Google Groups "Google AdMob Ads Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-admob-ads...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Giuseppe Iuculano

unread,
Jan 18, 2014, 4:12:17 AM1/18/14
to google-adm...@googlegroups.com
My nexus5 updated the Google play services yesterday and now I've the exact same problem....

Giuseppe Iuculano

unread,
Jan 18, 2014, 6:46:45 AM1/18/14
to google-adm...@googlegroups.com
I confirm that if I build an apk with updated GPS lib ads are showing... do I need to push an update?

Eddie Lee

unread,
Jan 18, 2014, 7:23:54 AM1/18/14
to google-adm...@googlegroups.com
Even we update it with the latest version. So how about if my user didn't update my apps? So I cannot get any ad because of this? From experience even after a months, only 50% of the user will update to the latest version. Admob should make a version which is compatible with the previous one.

If google update the play service library again next time, then we will need to ask our user to update it? 


2014/1/18 Giuseppe Iuculano <gius...@iuculano.it>
I confirm that if I build an apk with updated GPS lib ads are showing... do I need to push an update?

Il giorno sabato 18 gennaio 2014 10:12:17 UTC+1, Giuseppe Iuculano ha scritto:
My nexus5 updated the Google play services yesterday and now I've the exact same problem....

--

Giuseppe Iuculano

unread,
Jan 18, 2014, 8:20:23 AM1/18/14
to google-adm...@googlegroups.com
Sure, it needs to be fixed by Google


2014/1/18 Giuseppe Iuculano <gius...@iuculano.it>
To unsubscribe from this group and stop receiving emails from it, send an email to google-admob-ads-sdk+unsub...@googlegroups.com.

Eric Leichtenschlag

unread,
Jan 21, 2014, 5:48:43 PM1/21/14
to google-adm...@googlegroups.com
Hi Giuseppe,

Do you have timestamps on those logs? AdMob mediation currently times out after 5 seconds when trying to fetch an ad from a mediation network. That 5s is consistent throughout all SDKs though.

Also, the log statement "I/Ads     ( 5474): Ad is not visible. Not refreshing ad." indicates that your app (or activity containing the ad) is in the background. Is that true? Are you calling adView.pause() in your Activity's onPause() method?

Thanks,
Eric

Eric Leichtenschlag

unread,
Jan 21, 2014, 7:17:42 PM1/21/14
to google-adm...@googlegroups.com
These logs also indicate simultaneous ad requests are being made, which adds to the confusion.

Eric Leichtenschlag

unread,
Jan 21, 2014, 10:06:35 PM1/21/14
to google-adm...@googlegroups.com
Forget my previous statements, this is related to this bug when using the 4.0 library and the 4.1 service that just got pushed to user devices last week. The fix for now is to upgrade to the 4.1 library which solves this problem. We're also investigating if an update can be made to the service so it works properly with the 4.0 library.

Thanks,
Eric
--

Eric Leichtenschlag | Developer Programs Engineer | eleich...@google.com

Reply all
Reply to author
Forward
0 new messages