Massive number of ANRS: WAKE UP CALL FOR ADMOB TEAM

[Bog]

Hello

In past half a year Admob Team introduced a bug into Admob SDK for Unity, which is causing a massive number of ANRs. 

This bug has enormous negative consequences for developers who rely on Admob for monetisation, and most of us can't do anything about it. The only solution is to do not show ads for some of Android version, but newer one sometimes trigger enough ANRs to cross "Bad Behaviour" threshold. This bug has extremely negative consequences for developers, since Google Play severely punishes apps even for slight increase in rate of ANRs.

If you'll search this forum for "ANR" you find more than 20 threads with developers who are looking for solutions to this bug: it usually includes a line with "policy_ads_fdr_dynamite".

For first 3 months Admob Team basically ignored the issue and then started to attribute it to WebKit bug to avoid any responsibility. But this is Admob's issue, it's caused by Admob SDK for Unity: if you do not show ads - you have 0 ANRs.

Right now we believe that Admob Team doesn't do enough to finally fix this horrible bug, they've been "investigating" the issue without any success for more than 6 months.

Since this forum is the only option to voice this issue: WE URGE ADMOB TEAM TO FINALY WAKE UP, TAKE PROPER ACTIONS TO MITIGATE THIS ISSUE.

[Mobile Ads SDK Forum Advisor]

Hi Bog,

Thank you for bringing this concern to our attention. With all cases brought here, we have looked into them very deeply and with the thought of the User in mind. While we know that ANR's have been a problem for users. Do know that we have done everything that we can to look into this and help resolve this as best we can. With that in mind, if you have a specific instance of ANR happening in your app please let us know and we will happily look into it. At the same time, we ask for your patience as these are large complex systems and may sometimes take time for us to be able to find the solution.

Regards,

William Pescherine Mobile Ads SDK Team

ref:_00D1U1174p._5004Q2OUNOF:ref

[Bog]

Thank you for a reply, ANR log is exactly the same as have been reported and you already seen.

Please wake up. Please stop ignoring this issue. It's been enough time since April for you to properly investigate this issue. BUT YOU DIDN'T DO ANYTHING.

You even didn't provide ways how can people mitigate consequences of this bug. 

  #00  pc 00000000000706b4  /system/lib64/libc.so (nanosleep+8)

  #00  pc 000000000045c424  /data/app/com.***-EUapkJ4qMS_Ioaa1VDF8PQ==/lib/arm64/libil2cpp.so (???)

  #00  pc 000000000046902c  /data/app/com.***-EUapkJ4qMS_Ioaa1VDF8PQ==/lib/arm64/libil2cpp.so (???)

  #00  pc 000000000047b2e4  /data/app/com.***-EUapkJ4qMS_Ioaa1VDF8PQ==/lib/arm64/libil2cpp.so (???)

  #00  pc 000000000043ce10  /data/app/com.***-EUapkJ4qMS_Ioaa1VDF8PQ==/lib/arm64/libil2cpp.so (???)

  #00  pc 00000000002d62c4  /data/app/com.***-EUapkJ4qMS_Ioaa1VDF8PQ==/lib/arm64/libunity.so (???)

  #00  pc 000000000017ad08  /data/app/com.***-EUapkJ4qMS_Ioaa1VDF8PQ==/lib/arm64/libunity.so (???)

  #00  pc 000000000017ac20  /data/app/com.***-EUapkJ4qMS_Ioaa1VDF8PQ==/lib/arm64/libunity.so (???)

  at com.unity3d.player.ReflectionHelper.nativeProxyInvoke (Native method)

  at com.unity3d.player.ReflectionHelper.a (unavailable)

  at com.unity3d.player.ReflectionHelper$1.invoke (unavailable)

  at java.lang.reflect.Proxy.invoke (Proxy.java:1006)

  at com.google.android.gms.ads.initialization.OnInitializationCompleteListener.onInitializationComplete

  at com.google.android.gms.internal.ads.zzbdx.zzb

  at com.google.android.gms.internal.ads.zzbnp.zzbK

  at com.google.android.gms.internal.ads.zzhr.onTransact

  at android.os.Binder.transact (Binder.java:675)

  at mn.bi (com.google.android.gms.policy_ads_fdr_dynamite@212910700@212910700057.385466565.385466565:2)

  at com.google.android.gms.ads.internal.initialization.f.e (com.google.android.gms.policy_ads_fdr_dynamite@212910700@212910700057.385466565.385466565)

  at com.google.android.gms.ads.nonagon.initialization.c.run (com.google.android.gms.policy_ads_fdr_dynamite@212910700@212910700057.385466565.385466565:2)

  at android.os.Handler.handleCallback (Handler.java:907)

  at android.os.Handler.dispatchMessage (Handler.java:105)

  at atb.a (com.google.android.gms.policy_ads_fdr_dynamite@212910700@212910700057.385466565.385466565)

  at com.google.android.gms.ads.internal.util.f.a (com.google.android.gms.policy_ads_fdr_dynamite@212910700@212910700057.385466565.385466565:1)

  at atb.dispatchMessage (com.google.android.gms.policy_ads_fdr_dynamite@212910700@212910700057.385466565.385466565)

  at android.os.Looper.loop (Looper.java:216)

  at android.app.ActivityThread.main (ActivityThread.java:7625)

  at java.lang.reflect.Method.invoke (Native method)

  at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run (RuntimeInit.java:524)

  at com.android.internal.os.ZygoteInit.main (ZygoteInit.java:987)

понедельник, 27 сентября 2021 г. в 16:06:45 UTC+3, mobileadssdk:

[Roman]

Hello

To be precise this issue was reported more than year ago. And Admob team ignores it since then 

https://github.com/googleads/googleads-mobile-unity/issues/1475

[Mobile Ads SDK Forum Advisor]

Hi Roman,

I work along with William. Allow me to assist you in this.

As per checking, this has been flagged by other publishers and the team is aware of this. Currently, this is under investigation. We'll let you know the soonest we have our findings.

Regards,

Teejay Wennie Pimentel Mobile Ads SDK Team

ref:_00D1U1174p._5004Q2OUNOF:ref

[Roman]

Hello William

We heard this already - nothing is done so far. Right now those ANRs have a severely negative impact on every aspect of apps performance. 

Google Play ruthlessly punishes apps even for slight rate of ANRs.

We believe you should cooperate with Google Play team and exclude them from Android Vitals.

Since they have nothing to do with quality of apps. It's your bug.

[Mobile Ads SDK Forum Advisor]

Hi Roman,

Thank you for the response. We understand the frustration with things like this. But I know that it has been getting alot of attention from our teams. From what I have seen recently, they believe the recent update should help to relieve some of this issue. But are aware that it still needs to be looked into more. If you have more information to pass along please do, so that we can send it to our team and see what they have to say.

Regards,

William Pescherine Mobile Ads SDK Team

ref:_00D1U1174p._5004Q2OUNOF:ref

[Roman]

Hello William,

Good news, do you mean the Unity plugin update that was released 6 days ago, or forthcoming?

Thanks

[Mobile Ads SDK Forum Advisor]

Hi Roman,

Yes, my colleague is referring to Google Mobile Ads Unity Plugin v6.1.1, However, the recent update should help to relieve some of this issue, but are aware that it still needs to be looked into more.

Regards,

Teejay Wennie Pimentel Mobile Ads SDK Team

ref:_00D1U1174p._5004Q2OUNOF:ref

[Roman]

Hello

We're updated Unity Plugin to v6.1.1, still seeing Admob triggered ANRs:

Lenovo Tab M10 HD (2nd Gen)  Android 10 (SDK 29)

  #00  pc 000000000007f33c  /apex/com.android.runtime/lib64/bionic/libc.so (syscall+28)

  #00  pc 000000000014b094  /apex/com.android.runtime/lib64/libart.so (art::ConditionVariable::WaitHoldingLocks(art::Thread*)+148)

  #00  pc 00000000003c36c8  /apex/com.android.runtime/lib64/libart.so (art::JNI::NewString(_JNIEnv*, unsigned short const*, int)+448)

  #00  pc 0000000002f1030c  /data/app/com.google.android.webview-UjXonZONX9pIRdVOx9VheQ==/base.apk!libmonochrome.so (???)

  #00  pc 0000000002f0ea24  /data/app/com.google.android.webview-UjXonZONX9pIRdVOx9VheQ==/base.apk!libmonochrome.so (???)

  #00  pc 0000000002f0eb7c  /data/app/com.google.android.webview-UjXonZONX9pIRdVOx9VheQ==/base.apk!libmonochrome.so (???)

  #00  pc 0000000002138600  /data/app/com.google.android.webview-UjXonZONX9pIRdVOx9VheQ==/base.apk!libmonochrome.so (???)

  #00  pc 00000000020a5208  /data/app/com.google.android.webview-UjXonZONX9pIRdVOx9VheQ==/base.apk!libmonochrome.so (???)

  #00  pc 0000000002ec97d4  /data/app/com.google.android.webview-UjXonZONX9pIRdVOx9VheQ==/base.apk!libmonochrome.so (???)

  #00  pc 0000000002ed840c  /data/app/com.google.android.webview-UjXonZONX9pIRdVOx9VheQ==/base.apk!libmonochrome.so (???)

  #00  pc 0000000002f05458  /data/app/com.google.android.webview-UjXonZONX9pIRdVOx9VheQ==/base.apk!libmonochrome.so (???)

  #00  pc 0000000002f0540c  /data/app/com.google.android.webview-UjXonZONX9pIRdVOx9VheQ==/base.apk!libmonochrome.so (???)

  #00  pc 0000000002f051cc  /data/app/com.google.android.webview-UjXonZONX9pIRdVOx9VheQ==/base.apk!libmonochrome.so (???)

  #00  pc 0000000000018074  /system/lib64/libutils.so (android::Looper::pollInner(int)+860)

  #00  pc 0000000000017c78  /system/lib64/libutils.so (android::Looper::pollOnce(int, int*, int*, void**)+56)

  #00  pc 00000000001392bc  /system/lib64/libandroid_runtime.so (android::android_os_MessageQueue_nativePollOnce(_JNIEnv*, _jobject*, long, int)+44)

  at android.os.MessageQueue.nativePollOnce (Native method)

  at android.os.MessageQueue.next (MessageQueue.java:336)

  at android.os.Looper.loop (Looper.java:174)

  at android.app.ActivityThread.main (ActivityThread.java:7403)

  at java.lang.reflect.Method.invoke (Native method)

  at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run (RuntimeInit.java:502)

  at com.android.internal.os.ZygoteInit.main (ZygoteInit.java:980)

[Roman]

Situation remains critical, massive amount of ANRs, nothing is fixed.

Spikes are likely related to some type of ads, or ads serving problems , because they come and go in waves - nothing for a day or two and then lots of them.

  at java.lang.Object.wait (Native method)

  at java.lang.Object.wait (Object.java:442)

  at java.lang.Object.wait (Object.java:568)

  at com.google.android.gms.ads.exoplayer3.n.d (com.google.android.gms.policy_ads_fdr_dynamite@212910700@212910700000.385466565.385466565:2)

  at com.google.android.gms.ads.internal.video.exoplayer3.ab.at (com.google.android.gms.policy_ads_fdr_dynamite@212910700@212910700000.385466565.385466565:3)

  at com.google.android.gms.ads.internal.video.gmsg.exoplayer3.d.e (com.google.android.gms.policy_ads_fdr_dynamite@212910700@212910700000.385466565.385466565)

  at com.google.android.gms.ads.internal.webview.ac.aS (com.google.android.gms.policy_ads_fdr_dynamite@212910700@212910700000.385466565.385466565)

  at com.google.android.gms.ads.internal.webview.ac.destroy (com.google.android.gms.policy_ads_fdr_dynamite@212910700@212910700000.385466565.385466565:7)

  at com.google.android.gms.ads.internal.webview.y.destroy (com.google.android.gms.policy_ads_fdr_dynamite@212910700@212910700000.385466565.385466565:5)

  at com.google.android.gms.ads.internal.webview.q.f (com.google.android.gms.policy_ads_fdr_dynamite@212910700@212910700000.385466565.385466565:2)

  at com.google.android.gms.ads.internal.gmsg.y.a (com.google.android.gms.policy_ads_fdr_dynamite@212910700@212910700000.385466565.385466565:4)

  at com.google.android.gms.ads.internal.webview.q.i (com.google.android.gms.policy_ads_fdr_dynamite@212910700@212910700000.385466565.385466565:3)

  at com.google.android.gms.ads.internal.webview.q.e (com.google.android.gms.policy_ads_fdr_dynamite@212910700@212910700000.385466565.385466565:9)

  at com.google.android.gms.ads.internal.webview.ai.run (com.google.android.gms.policy_ads_fdr_dynamite@212910700@212910700000.385466565.385466565:4)

  at android.os.Handler.handleCallback (Handler.java:883)

  at android.os.Handler.dispatchMessage (Handler.java:100)

  at ati.a (com.google.android.gms.policy_ads_fdr_dynamite@212910700@212910700000.385466565.385466565)

  at com.google.android.gms.ads.internal.util.f.a (com.google.android.gms.policy_ads_fdr_dynamite@212910700@212910700000.385466565.385466565:1)

  at ati.dispatchMessage (com.google.android.gms.policy_ads_fdr_dynamite@212910700@212910700000.385466565.385466565)

  at android.os.Looper.loop (Looper.java:214)

  at android.app.ActivityThread.main (ActivityThread.java:7391)

  at java.lang.reflect.Method.invoke (Native method)

  at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run (RuntimeInit.java:492)

  at com.android.internal.os.ZygoteInit.main (ZygoteInit.java:980)

[Roman]

Admob team, are you okay? Are you conscious?

More than a year this bug persist, nothing is done to fix it.

We removed almost 30% of apps from showing ads, we banned literally thousands of devices and we're still getting enough ANRs to cross critical threshold.

It's disgrace

[Mobile Ads SDK Forum Advisor]

Hi Roman,

I understand the impact on this issue on your end. Please be informed that the team is actively working on this. In the meantime, we would recommend to keep an eye on our release notes regarding this.

[Roman]

Hello

Okay, please investigate the bursting nature of this bug, it happens in waves: nothing for a couple days, then suddenly a burst with many ANR's. From the outside it looks like some Ad serving problem

[Mobile Ads SDK Forum Advisor]

Hi Roman,

Thank you for the response. We would ask if you can get some more stacktraces or any reports of what is happening during these ANR. So that we can pass it along to our team to add to what we already have concerning this. Also have you been able to get any Charles logs that might point to a bad creative?

Regards,

William Pescherine Mobile Ads SDK Team

ref:_00D1U1174p._5004Q2OUNOF:ref

[Roman]

Hello

We're unable to reproduce this bug, but there is more stacktraces (it's a bit different, but they all come from the same bug):

Lenovo Tab M8

Broadcast of Intent { act=android.intent.action.SCREEN_OFF flg=0x50200010 }

  #00  pc 000000000007f33c  /apex/com.android.runtime/lib64/bionic/libc.so (syscall+28)

  #00  pc 000000000014b094  /apex/com.android.runtime/lib64/libart.so (art::ConditionVariable::WaitHoldingLocks(art::Thread*)+148)

  #00  pc 000000000038747c  /apex/com.android.runtime/lib64/libart.so (art::JNI::NewLocalRef(_JNIEnv*, _jobject*)+436)

  #00  pc 0000000002f10820  /data/app/com.google.android.webview-pGXjZl9WkqqTjYW282spBA==/base.apk!libmonochrome.so (???)

  #00  pc 00000000017add48  /data/app/com.google.android.webview-pGXjZl9WkqqTjYW282spBA==/base.apk!libmonochrome.so (???)

  #00  pc 00000000017ad888  /data/app/com.google.android.webview-pGXjZl9WkqqTjYW282spBA==/base.apk!libmonochrome.so (???)

  #00  pc 00000000017ad8cc  /data/app/com.google.android.webview-pGXjZl9WkqqTjYW282spBA==/base.apk!libmonochrome.so (???)

  #00  pc 00000000021bc434  /data/app/com.google.android.webview-pGXjZl9WkqqTjYW282spBA==/base.apk!libmonochrome.so (???)

  #00  pc 00000000021bc414  /data/app/com.google.android.webview-pGXjZl9WkqqTjYW282spBA==/base.apk!libmonochrome.so (???)

  #00  pc 00000000021bc414  /data/app/com.google.android.webview-pGXjZl9WkqqTjYW282spBA==/base.apk!libmonochrome.so (???)

  #00  pc 00000000021bc414  /data/app/com.google.android.webview-pGXjZl9WkqqTjYW282spBA==/base.apk!libmonochrome.so (???)

  #00  pc 0000000002ec7530  /data/app/com.google.android.webview-pGXjZl9WkqqTjYW282spBA==/base.apk!libmonochrome.so (???)

  #00  pc 00000000023a5140  /data/app/com.google.android.webview-pGXjZl9WkqqTjYW282spBA==/base.apk!libmonochrome.so (???)

  #00  pc 00000000023a5718  /data/app/com.google.android.webview-pGXjZl9WkqqTjYW282spBA==/base.apk!libmonochrome.so (???)

  #00  pc 00000000017b83a0  /data/app/com.google.android.webview-pGXjZl9WkqqTjYW282spBA==/base.apk!libmonochrome.so (???)

  #00  pc 00000000017b8428  /data/app/com.google.android.webview-pGXjZl9WkqqTjYW282spBA==/base.apk!libmonochrome.so (???)

  at J.N.MQGusfGb (Native method)

  at Z8.run (chromium-TrichromeWebViewGoogle.aab-stable-460607133:2)

  at Ck.a (chromium-TrichromeWebViewGoogle.aab-stable-460607133:5)

  at Ak.handleMessage (chromium-TrichromeWebViewGoogle.aab-stable-460607133:5)

  at android.os.Handler.dispatchMessage (Handler.java:107)

  at android.os.Looper.loop (Looper.java:214)

  at android.app.ActivityThread.main (ActivityThread.java:7405)

  at java.lang.reflect.Method.invoke (Native method)

  at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run (RuntimeInit.java:502)

  at com.android.internal.os.ZygoteInit.main (ZygoteInit.java:980)

[Roman]

The latest two are from the app with Google Mobile Ads Unity Plugin v6.1.1 and Unity v 2020.3.18f1

[Mobile Ads SDK Forum Advisor]

Hi Roman,

Thank you for the stacktrace. I was able to capture it and pass it along to our team to review. Once they are able to give some feedback on it we will be certain to let you know.

[Roman]

Hello,

Do you mean you've been able to reproduce this bug?

[Mobile Ads SDK Forum Advisor]

Hello Roman,

Thank you for your response. 

What my colleague means is that he was able to get the logs and share it to the rest of the team for further investigation. Please do note that the team is actively working on this, and we humbly ask for your patience here in the meantime. We will update you once we have more information. 

Regards,

Princess Pamela Pineda Mobile Ads SDK Team

 

ref:_00D1U1174p._5004Q2OUNOF:ref

[Bog]

Hello

Dear Admob team, this issue has been devastating for our app: each 3-4 days a new wave of these ANRs from random set of devices, we've tried everything: not showing ads for older versions of Android, updating to latest Unity Plugin,  we excluded hundreds of devices. The only thing that works - not showing Admob Ads. So the issue is clearly in Admob.

Since there was no progress for more than a year already towards finally fixing this issue, and everything we heard so far from your side was "we're investigating", we're seriously considering ditching Admob.

So there goes the question: guys, do you really have any plans to properly address this critical issue, have you been able to make any real progress towards solving it?

четверг, 14 октября 2021 г. в 12:56:51 UTC+3, mobileadssdk:

[Mobile Ads SDK Forum Advisor]

Hello Bog,

Thank you for your response.

I understand the urgency of your concern. Please do note that the team is actively working on this, and we humbly ask for your patience here in the meantime.

[Roman]

Hello

I see that GMA Unity Plugin v6.1.2 was released yesterday. But notes don't contain any mention of this anr bug fix, do you have any information whether it has been fixed in this release? 

Thank you

[Roman]

I also gathered topics posted on this forum in past 6 months related to the same issue, so Admob team could finally realize how massive this issue is.

https://groups.google.com/g/google-admob-ads-sdk/c/67InuYFeuPg/m/3zJW1CX4AgAJ

(Gameloft - huge publisher) https://groups.google.com/g/google-admob-ads-sdk/c/67InuYFeuPg/m/3zJW1CX4AgAJ

https://groups.google.com/g/google-admob-ads-sdk/c/f7K_VFrBHes/m/DHbeXRwgBAAJ

https://groups.google.com/g/google-admob-ads-sdk/c/5pFFVlXT9KY/m/EelaTJnbAgAJ

https://groups.google.com/g/google-admob-ads-sdk/c/0OAwvNqFWeI/m/qxys9MZ7AAAJ

https://groups.google.com/g/google-admob-ads-sdk/c/vj2GJN0LAdg/m/XSIPmvebAAAJ

https://groups.google.com/g/google-admob-ads-sdk/c/n6ICjD7JyK4/m/5ghyW7NJBgAJ

https://groups.google.com/g/google-admob-ads-sdk/c/6O7rEeJNSX0/m/oTMyL-j2CwAJ

[Mobile Ads SDK Forum Advisor]

Hi Roman,

Thank you for following up. Allow me to ask the team regarding the new version release. I'll let you know the soonest they provide their feedback.

[ca...@degoo.com]

I can confirm what other developers are saying. We're seeing thousands of ANRs per day related to AdMob. Seems to be a deadlock related to the init of the WebView. We're above the bad behavior threshold because of this. Being punished by Google because of bugs created by Google is an interesting situation, to put it mildly. 

[Mobile Ads SDK Forum Advisor]

Hi,

Thank you all for your patience, we understand the frustration of waiting to hear about an update. We have reached out to our team and at this moment have nothing that we can pass along. As previously stated here, I will make certain that our team knows that you are looking to get more information about this, or when a new release will be out.

Regards,

William Pescherine Mobile Ads SDK Team

ref:_00D1U1174p._5004Q2OUNOF:ref

[Roman]

Hello William,

Sorry but you don't understand our frustrations: for almost a year Admob team ignored and denied the issue, and after numerous attempts to bring the problem to your attention finally about 2 months ago you've started "investigating" it.

Since then there is no progress besides your misleading assurance that previous release of Unity Plugin "should relieve the issue", and each day we see new ANRs which suffocate our apps.

You didn't even come up with some guidance for developer on how to mitigate consequences.

So basically there is zero trust that you even currently "investigating" this issue and something will be done in near future. 

The also comes the question: if you do understand consequences, anger and frustration of affected developers, why don't you team up with Google Play to mitigate consequences of your bug if you was unable to fix it in more than a year?

It's extremely surreal and bizarre situation

[ca...@degoo.com]

I agree with Roman. Saying that you understand our situation when you're clearly doing nothing is an insult to our intelligence.

Here's the situation from our perspective:

Google: your app has too many ANRs. We will punish you by lowering your ranking and your revenue.

Us: we'll happily solve it. Could you provide some more details?

Google: the only info we can give you is this stack trace.

Us: the stack trace shows that this bug is caused by Google. Could you fix it?

Google: no, we won't fix it unless you provide us more info about the bug.

Us: you were the one who brought it up. You have the info.

Google: sorry, no info, no fix. But we will keep punishing you.

Us: ok, I'll have no option than to take a pay cut then. I'll tell my kids this is the reason they have less than other kids on the street.

It's like straight out of a Kafka novel. If you can't fix it then at the very least sync with Google Play so that we're not punished for it.

[Bog]

Hello

We’re agree with all that was said in previous comments. We also see a number of new ANRs is rising in newever versions of Android ( 9 - 11).

Things get worse and worse each day. Admob team, what is your plan for tackling this issue? 

Please provide a concrete response what are you doing to solve this? When it will be fixed? Who is reponsible for this mess?

четверг, 21 октября 2021 г. в 09:35:44 UTC+3, ca...@degoo.com:

[Roman]

Hey Admob team,

This issue won't resolve if you'll will pretend that it doesn't exist. From our side we're going to launch public campaign with posts on Medium, Reddit and other outlets about this situation and how your handle it...

I personally gonna reach people on LinkedIn in management from your company to tell them about this problem and how you screw up this.

We demand from you report about what is done to fix this bug and when it will be fixed?!

[Gregor Gjerek]

Google team please sort this out ASAP, we're also having issues - which we tried to debug and fix for like past few months and in the end we realised it's not even problem on our end.

petek, 22. oktober 2021 ob 13:56:45 UTC+2 je oseba Roman napisala:

[Bog]

Hello William

Why do you ignore this thread? We asked for status update on this issue. 

When it will be fixed?

суббота, 23 октября 2021 г. в 15:32:30 UTC+3, Gregor Gjerek:

[Roman]

Hello

Can confirm that updating app to Google Mobile Ads Unity Plugin v6.1.2 doesn't fix the problem.
Folks who also suffering this issue - please report this to your Admob account manager, we need to escalate it further.

People here saying they "actively working on the issue", but issue persist for about a year already, and there is little hope they will actually do something.

[ca...@degoo.com]

Hi,

Any updates on this? More specifically:

1. What's the ETA of solving the underlying issue?

2. What has the Google Play team said about stopping to punish developers for bugs that Google has caused?

Best,

Carl

[Roman]

Hello,

Someone has started a Github Issue related to this bug, please also post there your reports, maybe it will add visibility to the problem https://github.com/googleads/googleads-mobile-unity/issues/1825

[Roman]

Hello

What is the state of this bug? When it will be fixed?

[tonyev...@gmail.com]

When the new version will be fixed, please let me know

[Mobile Ads SDK Forum Advisor]

Hello Tony,

The ANR fix will be in the coming release, which has an ETA within April.

Thanks!


Regards,
Joshua

ref:_00D1U1174p._5004Q2OUNOF:ref

[XJIOP]

it's the end of April, and still no fixes.

суббота, 16 апреля 2022 г. в 03:16:49 UTC+2, mobileadssdk:

[Matej Špilár]

Hello guys, 

 I have been a long time lurker upon this thread and have been desperately waiting for fix. 

 Is the ETA end of April still valid ? 

Dátum: utorok 26. apríla 2022, čas: 20:13:51 UTC+2, odosielateľ: XJIOP

[Mobile Ads SDK Forum Advisor]

Hello Matej,

Thanks for reaching out.

We now expect the release with the fix will become available in ~2 weeks.

[Roman]

Hello

Can confirm that updating to v7.0.0 SDK Unity Plugin increased a number of ANRs for about 30% - 40%.

So fix is even more critical.

[Mobile Ads SDK Forum Advisor]

Hello Roman,

Thanks for reporting the issue.

We will have the fix for the ANR in the next Android release, which is expected to come in ~2 weeks. The Unity Plugin will then be updated shortly.

[Roman]

Hello

As you see from the spike of comment activity in this forum, as well on github related issues, latest update of SDK caused massive increase in ANRs.

We see the same thing in "Peer group" ANR level in Google Play Console that increased in past two weeks by ~15-20%.

What's happening? Where is the FIX?

Firebase team already fixed similar issue https://github.com/firebase/firebase-android-sdk/issues/2387

[Matej Špilár]

Hello again :) 

  two weeks are now gone - is there any update about the release schedule ? 

  I do not want to be rude or anything, but this is getting quite frustrating for many people.

  Thank you in advance! 

Dátum: sobota 30. apríla 2022, čas: 2:44:23 UTC+2, odosielateľ: mobileadssdk

[Roman]

Hello

Where is the fix?

[tonyev...@gmail.com]

When will the new version be released, please inform the exact date, if it cannot be released, please explain in advance, thank you

[tonyev...@gmail.com]

When will the new version be released, please inform the exact date, if it cannot be released, please explain in advance, thank you

[Mobile Ads SDK Forum Advisor]

Hello all,

Google Mobile Ads SDK version 21.0.0 is now available.

We have added manifest flags to optimize initialization and ad loading, please see Optimize initialization and ad loading guide for more details.

Thanks!


Regards,

[ca...@degoo.com]

We have now been running the updated version for more than a month and unfortunately, it made no difference. We're still above the bad behavior threshold for both crashes and ANRs due to the AdMob SDK. It's becoming clear what the root cause is. The root cause is not the ANR itself but mediocrity. They've tried their best to solve this for almost a year and it made no difference at all. Google engineers are not what they used to be. All the great ones have left to start their own companies and what's left is a Nirvana for average risk-averse middle managers. Google is the new IBM and no amount of effort from us publishers is going to change that. Better just to switch to a less inadequate SDK from a competing network. For instance, AppLovin MAX is showing great promise.

[tonyev...@gmail.com]

Updated to the new version, there are still a lot of anr issues

[Mobile Ads SDK Forum Advisor]

Hello Tony,

Thanks for letting us know.

Can you provide the (1) full stack trace from all threads and (2) steps to reproduce the ANR issue?

You can click "Reply to author" when you provide the above information.

[ca...@degoo.com]

Looks like Sundar has realized that the nonchalance Googlers displays toward its partners, like shown in this thread, is hurting the bottom line: https://arstechnica.com/gadgets/2022/08/google-ceo-calls-for-a-more-focused-and-efficient-google/

[XJIOP]

AdMob sdk 21.1.0

in the manifest
OPTIMIZE_INITIALIZATION
OPTIMIZE_AD_LOADING

in Application.class
MobileAds.initialize(this);

Triggered ANR in Activity.onPause { adView.pause(); }

[AndreasB]

Too bad no one high enough up the chain will ever have a look at this forum themselves. Between things like simply initializing the main product leading to ANRs across several major releases for years(!), which are then eventually fixed(?) with haphazard, barely documented optimization flags - or in other threads side products like Google's GDPR messaging solution still being totally dysfunctional and useless after more than two years - this should be considered a major problem for Google itself.

After all, this whole situation hurts not only individual developers. Last time I checked, a good portion of Google's revenue still came from exactly this product we're dealing with here. Every time some random app user doesn't get to see an ad, whether it is because their phone became unresponsive for no good reason or because they accidentally opted out of seeing ads altogether, or because of some other Google-caused issue - it hurts the bottom line. Every time a developer gives up on AdMob and implements a competitor's solution after having been asked for Charles logs, stack traces and whatnot for a dozen times for exactly the same problem - it hurts the bottom line.

If Sundar now has a letter box standing next to his office, requesting input on what needs to change - please, someone who is working there, just print out this thread and stuff it in there...

[ca...@degoo.com]

I couldn't have said it better myself. It seems like anyone with any work ethic has jumped ship a long time ago.

[Mobile Ads SDK Forum Advisor]

Hi XJIOP,

Thank you for reporting this ANR on pausing ad, this does appear different and we will need a full stack trace from all threads and  steps to reproduce. Also, you are experiencing an ANR in pausing an activity, not in requesting an ad or initializing the SDK. The best for narrowing down possibilities is reproducing the ANR in a sample app that only has slight modification and sending the project privately to us.

I am raising this issue with my team. We will get back to you as soon as possible.

Regards,

Aryeh Mobile Ads SDK Team

 

ref:_00D1U1174p._5004Q2d4Nku:ref

[Anton Petrov]

We are struggling with ANRs for a long time in our games and I think it is not AdMob SDK itself causing ANRs but a sum of factors.

We see a lot of ANRs caused by WebViews not only from the AdMob but from other networks as well.

AdMob dominates because it wins bidding and in fact the major part of ads impressions are from the AdMob.

I see problems are in the lack of communication between Google teams.

I imagine that AdMob team tests theirs Sample App and it works well (because it is lightweight) and they think all is great with the SDK.

Android OS developers do not care about effects introduced by legacy WebViews in older Androids, theirs goal is to release a new shiny Android version.

And finally the team behind Android Vitals does not care about all our struggles that we are making content-rich modern mobile games and some of us depend heavily on the organic traffic (staying below ANR threshold is a matter of life and death for small studios like us). 

They care about "the quality" and apply unrealistic fixed thresholds. 

Common, can you see the difference between one-screen word puzzle game and Genshin Impact or Diablo Immortal?

How on earth can you expect all games and all devices to fit this fixed threshold?

Do you really want to punish developers who make large fancy games?

I suggest Android Vitals team to ignore all ANRs which mention google products like WebView, Android Billing System, Firebase etc.

I suggest Android OS developers to redesign the main event loop so that it was not possible for a application to block it.

Make everything asynchronous, run callbacks in a thread pool. Do something, Apple has no notion of an ANR at all and everyone is happy.

Kind Regards

[Mobile Ads SDK Forum Advisor]

Hi Anton,

Thank you for the ANR report, we will look into what you have sent. That said, if you can upload a minimal sample application with specific steps to create the ANR, that will help us figure out what is happening.

Thanks,
Nick

ref:!00D1U01174p.!5004Q02d4Nku:ref

[Mobile Ads SDK Forum Advisor]

Hi Anton,

Regarding the ANR issue you reported. Can you please share the full bug report and stack trace which contains the full ANR trace? The thread causing this issue is thread 70, which is not included in the logs provided.

Looking forward to your response,
Nick

ref:!00D1U01174p.!5004Q02d4Nku:ref