E/Ads: Error waiting for future.

397 views
Skip to first unread message

nksys...@gmail.com

unread,
Oct 3, 2018, 12:51:02 PM10/3/18
to Google Mobile Ads SDK Developers
Hi,

I am trying to implement ads in my android app. I have used admob before on this app and it was working on production but recently stopped working. The app was taken down for a policy issue but since has been taken live again and I raised an appeal for admob to resume ads which was approved and that was quite some time back so I am pretty sure it is not an issue with waiting for my ads to work.

The code has not changed at all and since it was working before im sure thats not the problem.

The error is

10-03 22:13:41.592 2622-26113/? E/Ads: Error waiting for future.
    java.util.concurrent.ExecutionException: java.util.concurrent.TimeoutException
        at com.google.android.gms.ads.internal.util.future.ae.get(:com.google.android.gms@13280037@13.2.80 (100400-211705629):11)
        at com.google.android.gms.ads.internal.util.future.g.a(:com.google.android.gms@13280037@13.2.80 (100400-211705629):13)
        at com.google.android.gms.ads.internal.request.service.c.a(:com.google.android.gms@13280037@13.2.80 (100400-211705629):65)
        at com.google.android.gms.ads.internal.request.service.c.a(:com.google.android.gms@13280037@13.2.80 (100400-211705629):198)
        at com.google.android.gms.ads.internal.request.service.f.run(:com.google.android.gms@13280037@13.2.80 (100400-211705629):1)
        at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:458)
        at java.util.concurrent.FutureTask.run(FutureTask.java:266)
        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1167)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:641)
        at java.lang.Thread.run(Thread.java:764)
     Caused by: java.util.concurrent.TimeoutException
        at com.google.android.gms.ads.internal.util.future.m.run(Unknown Source:2)
        at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:458)
        at java.util.concurrent.FutureTask.run(FutureTask.java:266)
        at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:301)
        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1167) 
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:641) 
        at java.lang.Thread.run(Thread.java:764) 
10-03 22:13:41.598 21207-21240/com.google.android.gms.example.interstitialexample W/Ads: There was a problem getting an ad response. ErrorCode: 0
10-03 22:13:41.601 21207-21207/com.google.android.gms.example.interstitialexample W/Ads: Failed to load ad: 0


I am trying to load an interstitial ad, and I have tried the sample app with my application id and ad unit id with both test and production.

In test it would just show failed to load ad with error code 0.

 I am not sure If it is an issue for the application or ad from admob.

nksys...@gmail.com

unread,
Oct 3, 2018, 12:52:08 PM10/3/18
to Google Mobile Ads SDK Developers
Note I have tried searching for a response but havent had any luck so im trying posting about it here.

mobileadssdk-a...@google.com

unread,
Oct 3, 2018, 4:23:05 PM10/3/18
to nksys...@gmail.com, Google Mobile Ads SDK Developers
Hi there,

Thanks for reaching out to us. This is a known issue something which our team is actively working on. We will update you via this thread if we have any new information to share about the issue. 

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/
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~

On 10/03/18 12:51:02 nksys...@gmail.com wrote:
Hi,

I am trying to implement ads in my android app. I have used admob before on this app and it was working on production but recently stopped working. The app was taken down for a policy issue but since has been taken live again and I raised an appeal for admob to resume ads which was approved and that was quite some time back so I am pretty sure it is not an issue with waiting for my ads to work.

The code has not changed at all and since it was working before im sure thats not the problem.

The error is

10-03 22:13:41.592 2622-26113/? E/Ads: Error waiting for future.
    java.util.concurrent.ExecutionException: java.util.concurrent.TimeoutException
        at com.google.android.gms.ads.internal.util.future.ae.get(:com.google.android.gms@1328...@13.2.80 (100400-211705629):11)
        at com.google.android.gms.ads.internal.util.future.g.a(:com.google.android.gms@13280037@13.2.80 (100400-211705629):13)
        at com.google.android.gms.ads.internal.request.service.c.a(:com.google.android.gms@1328...@13.2.80 (100400-211705629):65)
        at com.google.android.gms.ads.internal.request.service.c.a(:com.google.android.gms@1328...@13.2.80 (100400-211705629):198)
        at com.google.android.gms.ads.internal.request.service.f.run(:com.google.android.gms@1328...@13.2.80 (100400-211705629):1)
        at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:458)
        at java.util.concurrent.FutureTask.run(FutureTask.java:266)
        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1167)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:641)
        at java.lang.Thread.run(Thread.java:764)
     Caused by: java.util.concurrent.TimeoutException
        at com.google.android.gms.ads.internal.util.future.m.run(Unknown Source:2)
        at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:458)
        at java.util.concurrent.FutureTask.run(FutureTask.java:266)
        at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:301)
        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1167) 
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:641) 
        at java.lang.Thread.run(Thread.java:764) 
10-03 22:13:41.598 21207-21240/com.google.android.gms.example.interstitialexample W/Ads: There was a problem getting an ad response. ErrorCode: 0
10-03 22:13:41.601 21207-21207/com.google.android.gms.example.interstitialexample W/Ads: Failed to load ad: 0
I am trying to load an interstitial ad, and I have tried the sample app with my application id and ad unit id with both test and production.

In test it would just show failed to load ad with error code 0.

 I am not sure If it is an issue for the application or ad from admob.

--

---
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/49e0dbc9-c9e7-4a48-9c05-bd504833ece7%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

nksys...@gmail.com

unread,
Oct 4, 2018, 12:11:36 PM10/4/18
to Google Mobile Ads SDK Developers
Hi,

Thank you for the quick update. Do you have any ETA on when this will get resolved? I understand that these things can take some time but I ask because I am in line with going to production in a week but will have to delay if ads do not work by then. Also I understand from testing that this only seems to be happening on Android O and P. Again an estimation of how long would be great.

PS: I understand that an ETA is not always possible so " We do not have an estimation as of now" is a perfectly acceptable response :)

mobileadssdk-a...@google.com

unread,
Oct 4, 2018, 3:21:10 PM10/4/18
to nksys...@gmail.com, Google Mobile Ads SDK Developers
Hi there,

Unfortunately, we don't provide ETAs for any issues. But, we will make sure that we update you via this thread if we have any updates from the team.

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.

cnd

unread,
Oct 5, 2018, 2:16:46 AM10/5/18
to Google Mobile Ads SDK Developers
We are also facing the same issue for Android O. It's a big issue affecting ad performance of the apps. Hope this gets resolved soon.

Bilal Shahid

unread,
Dec 24, 2018, 5:42:08 AM12/24/18
to Google Mobile Ads SDK Developers
 i am having the same problem and effecting widely. 

my logs:

W/Ads: Timed out waiting for ad response.
2018-12-24 15:37:03.662 18758-18758/org.chromium.chrome W/Ads: Failed to load ad: 2
2018-12-24 15:37:03.663 18758-18758/org.chromium.chrome E/Ads: errror rrrrr 2
2018-12-24 15:37:05.637 18758-18776/org.chromium.chrome W/Ads: java.util.concurrent.TimeoutException
        at java.util.concurrent.FutureTask.get(FutureTask.java:206)
        at com.google.android.gms.ads.internal.bb.a(:com.google.android.gms.dynamite_adsdynamite@14799081@14.7.99 (100400-223214910):46)
        at com.google.android.gms.ads.internal.a.a(:com.google.android.gms.dynamite_adsdynamite@14799081@14.7.99 (100400-223214910):130)
        at com.google.android.gms.ads.internal.request.c.a(:com.google.android.gms.dynamite_adsdynamite@14799081@14.7.99 (100400-223214910):95)
        at com.google.android.gms.ads.internal.request.p.a(:com.google.android.gms.dynamite_adsdynamite@14799081@14.7.99 (100400-223214910):6)
        at com.google.android.gms.ads.internal.request.y.a(:com.google.android.gms.dynamite_adsdynamite@14799081@14.7.99 (100400-223214910):4)
        at com.google.android.gms.ads.internal.request.ah.dispatchTransaction(:com.google.android.gms.dynamite_adsdynamite@14799081@14.7.99 (100400-223214910):3)
        at mu.onTransact(:com.google.android.gms.dynamite_adsdynamite@14799081@14.7.99 (100400-223214910):11)
        at android.os.Binder.execTransact(Binder.java:731)

mobileadssdk-a...@google.com

unread,
Dec 26, 2018, 5:02:07 PM12/26/18
to Bilal Shahid, Google Mobile Ads SDK Developers
Hi there,

Are you able to reproduce the issue with our sample apps? Can you please share the complete crash logs or crashlytics for us to take a look? Are you seeing these crashes on any specific devices or OS versions? What are the frequency of crashes? Are you seeing this with the latest version of our SDK?

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.
Reply all
Reply to author
Forward
0 new messages