AppLovin ANR in Admob mediation.

[Alex]

Hello,

I can see such ANRs in my Google Play console:

Thread 1

"main" tid=1 Runnable

Main Thread

at com.google.ads.mediation.applovin.AppLovinInitializer.access$000 (AppLovinInitializer.java:36) at com.google.ads.mediation.applovin.AppLovinInitializer$1.onSdkInitialized (AppLovinInitializer.java:121) at com.applovin.impl.sdk.o$2.run (SourceFile:1210) at android.os.Handler.handleCallback (Handler.java:883) at android.os.Handler.dispatchMessage (Handler.java:100) at android.os.Looper.loop (Looper.java:214) 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)

Thread 43

"UnityMain" tid=43 Native

UnityMain

#00 pc 0x000000000007f33c /apex/com.android.runtime/lib64/bionic/libc.so (syscall+28) #01 pc 0x00000000000829a4 /apex/com.android.runtime/lib64/bionic/libc.so (__futex_wait_ex(void volatile*, bool, int, bool, timespec const*)+140) #02 pc 0x00000000000e186c /apex/com.android.runtime/lib64/bionic/libc.so (pthread_cond_wait+60) #03 pc 0x000000000054fe98 /data/app/com.xxx.xxx -iiuP6kLRiE5BxciYSzXsTA==/lib/arm64/libunity.so #04 pc 0x0000000001e1aa88 ??? at com.unity3d.player.UnityPlayer.nativeRender (Native method) at com.unity3d.player.UnityPlayer.-$$Nest$mnativeRender (unavailable) at com.unity3d.player.UnityPlayer$F$a.handleMessage (unavailable) at android.os.Handler.dispatchMessage (Handler.java:103) at android.os.Looper.loop (Looper.java:214) at com.unity3d.player.UnityPlayer$F.run (unavailable)

Please help me fix it.

Stacktrace attached.

I am using:
Unity 2022.3.16

Google Mobile Ads Unity Plugin v8.6.0

AppLovin Unity Mediation Plugin 6.9.1

[Mobile Ads SDK Forum Advisor]

Hi Alex,

Thank you for contacting the Mobile Ads SDK Support team.

I will check with our team regarding your query and one of my team members will reach out to you once we have an update on this. Meanwhile, your patience is highly appreciated.

This message is in relation to case "ref:!00D1U01174p.!5004Q02r44VN:ref"

Thanks,
 

Mobile Ads SDK Team

 

[Mobile Ads SDK Forum Advisor]

Hi Alex,

After review of the stack trace the engineers determined that Google Mobile Ads is not involved in the main thread when the ANR happens.



ref:!00D1U01174p.!5004Q02r44VN:ref