Admob crashing : Error waiting for future

838 views
Skip to first unread message

Jerome Lanquetot

unread,
Sep 25, 2018, 3:07:56 AM9/25/18
to google-adm...@googlegroups.com
Hi, 

We are serving million of impressions per week on android but until a few days ago some players started to complain of not getting any ads. Nothing has changed on our side. I was able to reproduce a similar issue on one of my device, I integrated the new admob test suite and can see the different ad units and ads are served, but when I load ads through the game itself, it fails with the following error and logs: There was a problem getting an ad response. ErrorCode: 0.

Is there anything that has changed recently?

2018-09-25 00:07:47.577 4572-4898/? W/GodzilabEngine: LoadRewardedVideo(ca-app-pub-xxx)
2018-09-25 00:07:47.594 4572-4572/? I/Ads: Starting ad request.
2018-09-25 00:07:47.594 4572-4572/? I/Ads: SDK version: afma-sdk-a-v13280021.12451000.1
2018-09-25 00:07:47.594 4572-4572/? I/Ads: Use AdRequest.Builder.addTestDevice("2791DEAE5D5F92CEF2D2AACFF63E1DC6") to get test ads on this device.
2018-09-25 00:07:47.679 3464-3464/? W/Ads: #004 The webview is destroyed. Ignoring action.
2018-09-25 00:07:47.680 3464-3464/? W/Ads: #004 The webview is destroyed. Ignoring action.
2018-09-25 00:07:57.680 3464-16616/? 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 (040408-211705629):11)
        at com.google.android.gms.ads.internal.util.future.g.a(:com.google.android.gms@13280021@13.2.80 (040408-211705629):13)
        at com.google.android.gms.ads.internal.request.service.c.a(:com.google.android.gms@1328...@13.2.80 (040408-211705629):65)
        at com.google.android.gms.ads.internal.request.service.c.a(:com.google.android.gms@1328...@13.2.80 (040408-211705629):198)
        at com.google.android.gms.ads.internal.request.service.f.run(:com.google.android.gms@1328...@13.2.80 (040408-211705629):1)
        at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:457)
        at java.util.concurrent.FutureTask.run(FutureTask.java:266)
        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1162)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:636)
        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:457)
        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:1162) 
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:636) 
        at java.lang.Thread.run(Thread.java:764) 
2018-09-25 00:07:57.683 4572-6049/? W/Ads: There was a problem getting an ad response. ErrorCode: 0
2018-09-25 00:07:57.684 4572-4572/? W/Ads: Failed to load ad: 0

mobileadssdk-a...@google.com

unread,
Sep 25, 2018, 4:39:19 AM9/25/18
to google-adm...@googlegroups.com, jer...@godzilab-games.com
Hi Jerome,

Thank you for reaching out to us regarding this.

Please note that there is a known issue related to this that the team is actively investigating on. Rest assured that we will get back to you for any updates on this. 

On the other hand, based from our investigation, this seems to affect mostly Android O and P devices. Could you confirm if this is the same on your end?

Regards,
ivan Bautista
Mobile Ads SDK Team



--

---
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/f5d15743-6c17-4fa2-a8d1-e0fec210d089%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Jerome Lanquetot

unread,
Sep 25, 2018, 12:21:32 PM9/25/18
to google-adm...@googlegroups.com, mobileadssdk-a...@google.com
It seems to be O and P, from what we collected it's mostly Android 26+. Here is a list of the devices having the issue.

sm-j330f
sm-j330f
sm-a520w
sm-g930f
sm-g935v
sm-g950w
sm-g955f
sm-g960u
sm-g965f

And we have some pixels as well who reported the issue.


mobileadssdk-a...@google.com

unread,
Sep 26, 2018, 12:19:13 AM9/26/18
to Jerome Lanquetot, google-adm...@googlegroups.com
Hi Jerome,

Thank you for confirming that the devices affected by the issue on your end are mostly Android 26+. Please note that this is being prioritized by the team and we'll get back to this thread for any updates.

Regards,
Ivan Bautista
Mobile Ads SDK Team


On 09/25/18 15:07:56 jer...@godzilab-games.com wrote:
Hi, 

We are serving million of impressions per week on android but until a few days ago some players started to complain of not getting any ads. Nothing has changed on our side. I was able to reproduce a similar issue on one of my device, I integrated the new admob test suite and can see the different ad units and ads are served, but when I load ads through the game itself, it fails with the following error and logs: There was a problem getting an ad response. ErrorCode: 0.

Is there anything that has changed recently?

2018-09-25 00:07:47.577 4572-4898/? W/GodzilabEngine: LoadRewardedVideo(ca-app-pub-2793625110114106/8056085355)
2018-09-25 00:07:47.594 4572-4572/? I/Ads: Starting ad request.
2018-09-25 00:07:47.594 4572-4572/? I/Ads: SDK version: afma-sdk-a-v13280021.12451000.1
2018-09-25 00:07:47.594 4572-4572/? I/Ads: Use AdRequest.Builder.addTestDevice("2791DEAE5D5F92CEF2D2AACFF63E1DC6") to get test ads on this device.
2018-09-25 00:07:47.679 3464-3464/? W/Ads: #004 The webview is destroyed. Ignoring action.
2018-09-25 00:07:47.680 3464-3464/? W/Ads: #004 The webview is destroyed. Ignoring action.
2018-09-25 00:07:57.597 4572-4898/? I/GodzilabEngine: URL http://15000.gzidlerpg.appspot.com/guild/tick

Marco Batista

unread,
Sep 27, 2018, 4:42:00 AM9/27/18
to Google Mobile Ads SDK Developers
I'm also facing this issue.

I just tested on a Pixel 2 XL with Android 9.0 and I get the error even with the AdMob sample apps.

Best regards,
Marco Batista

Sylvain

unread,
Sep 27, 2018, 6:27:15 AM9/27/18
to Google Mobile Ads SDK Developers
Hi,
Also facing the same issue ... S7 Android 8.0.0
Cheers,


mobileadssdk-a...@google.com

unread,
Sep 27, 2018, 6:40:24 AM9/27/18
to Sylvain, Google Mobile Ads SDK Developers
Hi everyone,

Thank you for the extra details.

Please note that this issue is being highly prioritized by the team. Rest assured that we will get back on this thread for any updates.

Regards,
Ivan Bautista
Mobile Ads SDK Team



--

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

Jerome Lanquetot

unread,
Oct 4, 2018, 8:30:15 PM10/4/18
to mobileadssdk-a...@google.com, google-adm...@googlegroups.com
Any update regarding this issue?

On Tue, Sep 25, 2018 at 9:19 PM <mobileadssdk-a...@google.com> wrote:
Hi Jerome,

        at com.google.android.gms.ads.internal.util.future.ae.get(:com.google.android.gms@13280021@13.2.80 (040408-211705629):11)
        at com.google.android.gms.ads.internal.util.future.g.a(:com.google.android.gms@13280021@13.2.80 (040408-211705629):13)
        at com.google.android.gms.ads.internal.request.service.c.a(:com.google.android.gms@13280021@13.2.80 (040408-211705629):65)
        at com.google.android.gms.ads.internal.request.service.c.a(:com.google.android.gms@13280021@13.2.80 (040408-211705629):198)
        at com.google.android.gms.ads.internal.request.service.f.run(:com.google.android.gms@13280021@13.2.80 (040408-211705629):1)
        at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:457)
        at java.util.concurrent.FutureTask.run(FutureTask.java:266)
        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1162)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:636)
        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:457)
        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:1162) 
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:636) 
        at java.lang.Thread.run(Thread.java:764) 
2018-09-25 00:07:57.683 4572-6049/? W/Ads: There was a problem getting an ad response. ErrorCode: 0
2018-09-25 00:07:57.684 4572-4572/? W/Ads: Failed to load ad: 0

--

---
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...@googlegroups.com.
To post to this group, send email to google-adm...@googlegroups.com.

mobileadssdk-a...@google.com

unread,
Oct 5, 2018, 12:18:04 AM10/5/18
to google-adm...@googlegroups.com, jer...@godzilab-games.com
Hi Jerome,

Please note that there is a fix already in place for this, however, we can't provide any definite timelines on its release. Rest assured that this is a high priority.

Regards,
Ivan Bautista
Mobile Ads SDK Team




On 10/05/18 08:29:51 jer...@godzilab-games.com wrote:
Any update regarding this issue?

        at com.google.android.gms.ads.internal.util.future.ae.get(:com.google.android.gms@1328...@13.2.80 (040408-211705629):11)
        at com.google.android.gms.ads.internal.util.future.g.a(:com.google.android.gms@13280021@13.2.80 (040408-211705629):13)
        at com.google.android.gms.ads.internal.request.service.c.a(:com.google.android.gms@1328...@13.2.80 (040408-211705629):65)
        at com.google.android.gms.ads.internal.request.service.c.a(:com.google.android.gms@1328...@13.2.80 (040408-211705629):198)
        at com.google.android.gms.ads.internal.request.service.f.run(:com.google.android.gms@1328...@13.2.80 (040408-211705629):1)
        at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:457)
        at java.util.concurrent.FutureTask.run(FutureTask.java:266)
        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1162)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:636)
        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:457)
        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:1162) 
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:636) 
        at java.lang.Thread.run(Thread.java:764) 
2018-09-25 00:07:57.683 4572-6049/? W/Ads: There was a problem getting an ad response. ErrorCode: 0
2018-09-25 00:07:57.684 4572-4572/? W/Ads: Failed to load ad: 0

--

---
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 12, 2018, 3:30:22 PM10/12/18
to Google Mobile Ads SDK Developers
Any update on this issues?
There is a significant impact on ad performance on Android O devices because of this issue.

mobileadssdk-a...@google.com

unread,
Oct 15, 2018, 3:01:48 AM10/15/18
to cnd, Google Mobile Ads SDK Developers
Hi,

Thank you for following up on this. 

The fix is ready but we don't have a definite timeline on its release. However, do note that this is a high priority for the team.

Regards,
Ivan Bautista
Mobile Ads SDK Team


On 10/13/18 03:30:21 code...@gmail.com wrote:
Any update on this issues?
There is a significant impact on ad performance on Android O devices because of this issue.

--

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

Ju-tae Kim

unread,
Oct 22, 2018, 6:03:40 AM10/22/18
to Google Mobile Ads SDK Developers
Hi.

Could you explain the reason detaily and technically ?
I think,  I should update my app. with the new SDK, if the reason is in SDK,
Is it right ?





2018년 10월 15일 월요일 오후 4시 1분 48초 UTC+9, mobileadssdk-a...@google.com 님의 말:

mobileadssdk-a...@google.com

unread,
Oct 22, 2018, 11:43:54 PM10/22/18
to google-adm...@googlegroups.com, jtk...@gmail.com
Hi Ju-tae,

The issue in question throws an Internal Error and this mostly affects Android O & P devices. Please note that the fix is already in place for this, however, we can't provide any definite timeline on its release. Since this is a high priority, the team is doing its best to try to push the release as soon as possible. That said, we'll keep you posted for any new updates through this thread or you may keep an eye on our Release Notes for any future updates.

Regards,
Ivan Bautista
Mobile Ads SDK Team



On 10/22/18 18:03:40 jtk...@gmail.com wrote:
Hi.

Could you explain the reason detaily and technically ?
I think,  I should update my app. with the new SDK, if the reason is in SDK,
Is it right ?





2018년 10월 15일 월요일 오후 4시 1분 48초 UTC+9, mobileadssdk-a...@google.com 님의 말:
Hi,

Thank you for following up on this. 

The fix is ready but we don't have a definite timeline on its release. However, do note that this is a high priority for the team.

Regards,
Ivan Bautista
Mobile Ads SDK Team



On 10/13/18 03:30:21 code...@gmail.com wrote:
Any update on this issues?
There is a significant impact on ad performance on Android O devices because of this issue.

--

---
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+unsubscrib...@googlegroups.com.

--

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