Hi Alex,
Thank you for contacting the Mobile Ads SDK support team.
Could you please specify which version you're using? According to the release notes, the latest Version 8.0.3.. It's always recommended to use the most recent version to avoid conflicts, so please ensure you've integrated the latest one.
Please confirm that you have followed the instructions in AppLovin's MAX Test Mode guide to enable AppLovin test ads. Additionally, ensure that you have register your test device for AdMob and enable test mode in the AppLovin UI.
If you're still experiencing the issue after following the steps above, please share your sample project where you are facing the issue with us.
If the file(s) you are looking to share are less than 25mb in total you can attach them to this case on your next reply. If you are having trouble attaching your file to this case or if your file(s) are larger than 25mb, you can share your files with me by performing the following steps:
2. Fill out all fields, and attach your file(s).
3. Please reply back on this thread when you have uploaded your file(s). Please do not share this link.![]() |
Mobile Ads SDK Team |
Hi,
Thank you for getting back to us.
Please note that you shouldn't need to initialize the AppLovin SDK by yourselves, as both the adapter and the SDK will be initialized when the GMA SDK initializes. No additional steps are required for initialization.
As mentioned in Step 4: Implement privacy settings on AppLovin SDK, AppLovin supports reading the consent string from shared preferences and setting the consent status accordingly. Therefore, if publishers are already using a CMP SDK to set the consent string, they don't need to call setHasUserConsent() to pass the consent to the AppLovin SDK.
If the issue still persists, kindly provide the below information via reply to author option for further investigation: