-
Notifications
You must be signed in to change notification settings - Fork 102
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
onSdkInitialized method is not triggered when I initialize the SDK without an Activity. #673
Comments
Hey @mertkesgin! I have created a sample project in which the AppLovin SDK was initialized in a service without an Activity. However, I was unable to reproduce the issue, and the callback was invoked as expected. I believe the issue you are facing is due to you and AdMob Mediation trying to initialize our SDK simultaneously. While you are setting the mediation provider to "MAX", the logs show Please let me know if this fixes the callback issue for you. |
Even when I disable AdMob and initialize the AppLovin SDK, the same issue persists. Could you please add the following scenario to your sample project and test it again?
|
Hi @mertkesgin, thanks for checking. Would you be able to create a sample Android Studio project where this issue reproduces and share the project with me? This will allow me to investigate your use case directly. |
MAX SDK Version
12.5.0
Device/Platform Info
Android
Current Behavior
I am trying to initialize the SDK without Activity. Although the SDK is initialized, the onSdkInitialized method is not triggered.
I can see the following error in the logs;
This is how I know that the SDK is initialized even though the onSdkInitialized method is not triggered;
NOTE: When I initialize the SDK from an Activity, the onSdkInitialized method is triggered.
Expected Behavior
After initializing the SDK without Activity, the onSdkInitialized method must be triggered;
How to Reproduce
You can try to initialize the SDK without Activity.
Additional Info
No response
The text was updated successfully, but these errors were encountered: