AppLovin SDK initialization race caused by missing/incorrect documentation

[caro...@gmail.com]

Dependencies:

implementation 'com.google.android.gms:play-services-ads:23.2.0'

implementation 'com.google.ads.mediation:applovin:12.6.0.0'

Background:

AppLovin SDK introduced [new SDK init APIs](https://developers.applovin.com/en/android/overview/new-sdk-initialization-api/) for 12.4.0+, which asks users to initialize the SDK using the new API and remove the old AndroidManifest.xml metadata entries. 

However, there is no documentation on AdMob side that explains the order of initialization.

https://developers.google.com/admob/android/mediation/applovin

https://developers.google.com/admob/android/mediation/applovin#step_5_add_required_code

Furthermore, AdMob documentation specifically asks users to forward privacy settings before MobileAds.initialize(). 

https://developers.google.com/admob/android/mediation/applovin#step_4_implement_privacy_settings_on_applovin_sdk

This caused an init race between AdMob and AppLovinSDK, and may result in OnInitializationCompleteListener passed to MobileAds.initialize() not firing. It is because the privacy settings trigger AppLovinSDK's init sequence, which then triggers MobileAds init without a callback, causing later MobileAds.initialize calls with callbacks to be dropped.

Please add documentation about the order of initialization, order of privacy settings, and how to properly initialize AppLovinSDK 12.4.0+. Thanks!

[Mobile Ads SDK Forum Advisor]

Hi,

Thanks for contacting Mobile Ads SDK Support team.

Our team is investigating on your issue. One of our teammates contact you once we have update on this. Meanwhile your patiences is appreciated.
 

This message is in relation to case "ref:!00D1U01174p.!5004Q02vEiln:ref" (ADR-00262593)

Thanks,
 

Mobile Ads SDK Team