AppLovin / AppLovin-MAX-SDK-Android

Other
232 stars 104 forks source link

MaxHybridMRecAdActivity and MaxHybridNativeAdActivity crash when ad format is not the expected one #748

Open rubensousa opened 1 week ago

rubensousa commented 1 week ago

MAX SDK Version

13.0.1

Device/Platform Info

Android 14, 13, 12

Crashes/ANRs per Day

100

Percentage of Users Affected

1%

First Occurrence of Crash/ANR

Updated from 11.11.3, but I remember seeing this crash also for that version

Exception and Stack Trace

Caused by java.lang.IllegalStateException
Failed to fire display failed callback (null): neither interstitial nor app open ad
com.applovin.impl.ad.a (SourceFile:281)
com.applovin.impl.ad.a (SourceFile:110)
com.applovin.mediation.hybridAds.MaxHybridNativeAdActivity.onCreate (SourceFile:3)
android.app.Activity.performCreate (Activity.java:8305)
android.app.Activity.performCreate (Activity.java:8284)
android.app.Instrumentation.callActivityOnCreate (Instrumentation.java:1417)
android.app.ActivityThread.performLaunchActivity (ActivityThread.java:3626)
android.app.ActivityThread.handleLaunchActivity (ActivityThread.java:3782)
android.app.servertransaction.LaunchActivityItem.execute (LaunchActivityItem.java:101)
android.app.servertransaction.TransactionExecutor.executeCallbacks (TransactionExecutor.java:135)
android.app.servertransaction.TransactionExecutor.execute (TransactionExecutor.java:95)
android.app.ActivityThread$H.handleMessage (ActivityThread.java:2307)
android.os.Handler.dispatchMessage (Handler.java:106)
android.os.Looper.loopOnce (Looper.java:201)
android.os.Looper.loop (Looper.java:288)
android.app.ActivityThread.main (ActivityThread.java:7872)
java.lang.reflect.Method.invoke (Method.java)
com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run (RuntimeInit.java:548)
com.android.internal.os.ZygoteInit.main (ZygoteInit.java:936)

And also:

Caused by java.lang.IllegalStateException
Failed to fire display failed callback (null): neither interstitial nor app open ad
com.applovin.impl.ad.a (SourceFile:281)
com.applovin.impl.ad.a (SourceFile:110)
com.applovin.mediation.hybridAds.MaxHybridMRecAdActivity.onCreate (SourceFile:3)
android.app.Activity.performCreate (Activity.java:8305)
android.app.Activity.performCreate (Activity.java:8284)
android.app.Instrumentation.callActivityOnCreate (Instrumentation.java:1417)
android.app.ActivityThread.performLaunchActivity (ActivityThread.java:3626)
android.app.ActivityThread.handleLaunchActivity (ActivityThread.java:3782)
android.app.servertransaction.LaunchActivityItem.execute (LaunchActivityItem.java:101)
android.app.servertransaction.TransactionExecutor.executeCallbacks (TransactionExecutor.java:135)
android.app.servertransaction.TransactionExecutor.execute (TransactionExecutor.java:95)
android.app.ActivityThread$H.handleMessage (ActivityThread.java:2307)
android.os.Handler.dispatchMessage (Handler.java:106)
android.os.Looper.loopOnce (Looper.java:201)
android.os.Looper.loop (Looper.java:288)
android.app.ActivityThread.main (ActivityThread.java:7872)
java.lang.reflect.Method.invoke (Method.java)
com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run (RuntimeInit.java:548)
com.android.internal.os.ZygoteInit.main (ZygoteInit.java:936)

How to Reproduce

No sure, but this seems related to wrong ad formats being delivered. My app uses only native ad formats, but somehow the library detects requests for interstitials and app open ads, which is wrong.

Reproducible in the demo app?

Not Tested

Additional Info

I can provide additional info in your support channels if needed

applovinAsh commented 1 week ago

@rubensousa, are you able to reproduce the issue in your testing? If so, can you provide verbose logs from the start of a session? To enable verbose logs, see here: https://developers.applovin.com/en/max/faq/how-to-enable-verbose-logging-in-the-applovin-sdk

rubensousa commented 1 week ago

@applovinAsh Unfortunately, no. The issue is sporadic and only happens for some ads

applovinAsh commented 1 week ago

@rubensousa, thank you for that information. We have an active investigation and will update the thread when we have more information. If you can capture the issue, please provide the verbose logs.