The is the fix sent to me from Google (Part 2 of 2)
5. Under the new release page, you can:
6. Select Save.
7. When you've finished preparing your release, select Review release.
If the non-compliant version code is released to multiple tracks, repeat steps 3-7 in each track.
The is the fix sent to me from Google (Part 1 of 2)
In addition, if you want to deactivate a non-compliant version code. Please follow the below steps:
(Part 2 of 2) here v
construct.net/en/comments/68513
OK I resolved my issue. It turned out that the issue was in the google play store.
Google look at any previous uploads and if they have not reached the published stage then it through errors.
Ashley I currently have an issue where as when I export the signed android aab file and upload it to the Google play it complains that the advertisement ID permission has not been set in the androidmanifest.xml file. Apparently this is required once the software targets android 33 and above. The current plugin targets android 34. This is the error message:
Error
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.
If you don't include this permission in your manifest file, your advertising identifier will be zeroed out. This may break your advertising and analytics use cases, and cause loss of revenue. Learn more
Apps that target Android 13 (API 33) without the AD_ID permission will have their advertising identifier zeroed out. This may impact advertising
How can we fix this?
Member since 18 Jun, 2024