Skip to content
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

[Wiki] Add instructions about setting up / managing the mediation adapter extensions #27

Open
caroparo opened this issue Dec 24, 2023 · 3 comments

Comments

@caroparo
Copy link

caroparo commented Dec 24, 2023

New users seem to get confused about SDK warnings or errors from Google Play Console. Some apps got rejected (e.g. AppLovin SDK is no longer allowed for Families games).

@Markieboyyy
Copy link

did you find an answer to this issue? because google is saying this:
com.applovin:applovin-sdk com.applovin:applovin-sdk: Consider upgrading to a policy-compliant version of the SDK if available from your SDK provider, or removing the SDK.

@BenMiller3
Copy link

Following for an update.

@caroparo
Copy link
Author

This is a feature request for wiki update, and not a bug.

You can and should delete unwanted SDKs (e.g. AdMobAppLovin) from under the root AdMob extension. It is only a mediation adapter, and shouldn't cause a problem.

For more information on AdMob mediation adapters, please refer to
Google's official documentation for now.

In fact, if you don't use mediation at all, you should probably delete all child SDKs (AdMobAppLovin, AdMobIronSource, AdMobMeta, AdMobPangle, AdMobUnityAds) since they won't do anything without a proper setup and will only increase your build size.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: Backlog
Development

No branches or pull requests

5 participants