await AppLovinMAX.initialize(initAppLovinKey) is Taking huge time to init

[ycv005]

MAX Plugin Version

applovin_max: 3.8.0 and applovin_max: ^3.10.1

Flutter Version

Flutter (Channel stable, 3.22.0, on macOS 13.1 22C65 darwin-arm64, locale en-IN)

Device/Platform Info

Android

Current Behavior

I am currently initializing the AppLovinMAX SDK but it is taking so much time to init (more than 4-5 sec). I tried with 5G mobile data, 50 Mbps wifi, still same issue.

• I Thought to initialize AppLovinMAX SDK without await at starting but I fear and sure enough that Ads will not be display. Kindly, suggest or direct a better way to handle this. If this is an issue then how we can improve this. I have also google_mobile_ads but it initialize around 600 to 800 ms (milisecond).

Note

• I have also enable some of mediation network from AppLovin DashBoard (AppLovin, Google Admanager, Facebook, Unity). Does more mediation network effect initializing the AppLovinMAX SDK time ?
• Even in Debug mode, it is taking more time to initialize the AppLovinMAX SDK

Expected Behavior

Initializing the AppLovinMAX SDK should be fast enough.

How to Reproduce

• Try a Demo verion on Real and Actual environment where Actual Ads are displayed using AppLovin Flutter Package.

Additional Info

No response

[ycv005]

Does below step will be helpful?

• Initialize before creating MyApp i.e., using runApp (but without await). This will trigger to initialization to server.
• Now in my other Page like Splash Screen where MyApp will navigate first, then their again Initialize AppLovin SDK with await. I believe after this step, it will navigate to Home Page with AppLovin SDK completed initialization and then Ads will be visible.

Doubts

• What will be drawback of this step?
• Will it decrease time of initialization?

[ycv005]

@alhiwatan @thomasmso Can you please help here ?

[alhiwatan]

The SDK initialization time can vary depending on your network conditions and the specific ad networks you integrate, with some ad networks potentially taking longer than others. Using a splash screen during initialization is a good idea as it provides feedback to the user while they wait. However, this will probably not decrease the total initialization time. Ultimately, how you implement this to meet your goals is up to you.

[github-actions]

This issue is stale because it has been open for 30 days with no activity.