-
Notifications
You must be signed in to change notification settings - Fork 202
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
Android missing permission - com.google.android.gms.permission.AD_ID #562
Comments
👋 Hi @quachdev and Thank you for reaching out to us.
|
Same problem, We're losing money by not being able to place ads because of this. How much longer do we have to wait for this issue to be resolved?" Your advertising ID declaration in Play Console says that your app uses advertising ID. A manifest file in one of your active artifacts doesn't include the com.google.android.gms.permission.AD_ID permission. |
It's really incredible. Normally I had published ads in my previous version. I added banner ads to a few more screens. When I install the release aab bundle and proceed, I get the same error. There is no solution. I also look at bundle_manifest/release files. All of them have the "com.google.android.gms.permission.AD_ID" key . |
Have you solved it? |
Have you solved it? |
I couldn't solve the problem. I updated the statement in the play console to remove the ad. They closed my account without sending any warning or notification. Google Play is a regret |
Report
Plugin Version
6.14.3
(also tried6.13.1
)On what Platform are you having the issue?
android
What did you do?
upload the app to play store
What did you expect to happen?
no errors
What happened instead?
ℹ Please replace these two lines with of what happened instead.
Received the following error on upload:
Please provide any other relevant information.
Can see the file in the repo here: https://github.com/AppsFlyerSDK/appsflyer-react-native-plugin/blob/master/android/src/main/AndroidManifest.xml
Usure how to proceed or if missing anything when making the build.
The text was updated successfully, but these errors were encountered: