Google UMP Support and TCFv2.0 Compliance
As of AppLovin MAX SDK version 12.0.0, if you use Google’s CMP (UMP), MAX takes care of CMP integration and ensures that the consent status is established correctly when you initialize the SDK. See Google UMP Automation for more details. However, if you use a different CMP, you must perform this integration yourself and you must ensure that the CMP establishes the consent status correctly before you initialize the SDK.
Details on how consent is handled per network: https://dash.applovin.com/documentation/mediation/android/getting-started/privacy#tcf-v2.0-consent
If you access Google demand through MAX, it’s critical that you review the Google CMP requirements.
Other Changes
- Add nullability annotations for MAX listener APIs.
- Java 8 requirement.
- Fix
Fatal Exception: java.lang.OutOfMemoryError: pthread_create (1040KB stack) failed: Try again
OOMs. - Fix ANRs caused by
com.applovin.impl.sdk.a.f$1.run
. - Fix for
Fatal Exception: java.lang.RuntimeException: Canvas: trying to draw too large(xxx bytes) bitmap
for native ads. - Various other fixes including several for black screens.
- Fix template native ads using white text color on Android 6 making the text unreadable.
- Fix
Attempt to invoke virtual method 'java.lang.String com.applovin.impl.a.a.a.a.a()' on a null object reference
crash.
Mediation Debugger
- Various changes