adrianrhodes's Comments

  • The is the fix sent to me from Google (Part 2 of 2)

    5. Under the new release page, you can:

      • Upload a new, compliant version code and roll out a new release to 100% to completely deactivate the non-compliant version.
      • Roll out a blank release (i.e., a release with all version codes under the Deactivated app bundles section and no version codes under the New app bundles or Retained app bundles sections) and roll it out to 100%.

    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:

    1. Go to your Play Console.
    2. Select the app.
    3. Go to the track where the non-compliant version code is active.
      • You can confirm where the non-compliant version code is active by going to:
        1. Release > Releases overview > Add filter > Version code > Search > Apply
        2. Release > App bundle explorer > Search by version code or name > View app version (right arrow symbol)
    4. Near the top right of the page, click Create new release (you may need to click Manage track first).
      • If the release with the violating version code is in a draft state, discard the release.

    (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?

adrianrhodes's avatar

adrianrhodes

Member since 18 Jun, 2024

None one is following adrianrhodes yet!

Trophy Case

  • Jupiter Mission Supports Gordon's mission to Jupiter
  • Regular Visitor Visited Construct.net 7 days in a row
  • RTFM Read the fabulous manual
  • Email Verified

Progress

4/44
How to earn trophies