Skip to content

Latest commit

 

History

History
99 lines (58 loc) · 5.68 KB

learn-playconsole.md

File metadata and controls

99 lines (58 loc) · 5.68 KB

Learn Google Play Console

Quick Links:

Play Console Docs, Issues:

  • Set up an open, closed, or internal test | PlayConsole: Click here Amazing youtube video explanation about these three: Click here
  • Distribute app releases to specific countries: Click here
  • Issue - Google Play Alpha: App not available for this account: Click here

PlayStore notes:

  • Country availability is changed across all tracks.
  • There are some monetization and country availability exceptions for internal tests. For details, go to the section on setting up an internal test.
  • Paid apps: If you’re testing a paid app using an open or closed test, testers still need to purchase it. If you’re testing a paid app using an internal test, testers can install your app for free.

Initial Play Console App publishing to Production

First time review time taken by Play Console?

image

image

image

image

Publishing Overview:

image

image

image

Choose signing key

# Note: The `pepk.jar` file is from https://stackoverflow.com/a/52472918/10012446
# Note: I am using pepk.jar from above source because google's official `pepk-src.jar` file is not working and throws error when tried to use.
java -jar ./pepk.jar \
--keystore=./play-console-android-06-oct-2023.keystore \
--alias=$KEYSTORE_ALIAS \
--output=output.zip \
--include-cert --rsa-aes-encryption \
--encryption-key-path=./encryption_public_key.pem

image

image

image

ISSUE - Advertising id permission is not inlcuded in this build

  • Issue - A manifest file in one of your active artifacts doesn't include the AD_ID permission: Click here

The issue while publishing the app to any track, I was getting error that AdvertisingId permissino is not included in this build. The issue is described better here -

The solution of this error is that it was complaining on behalf of older build in other tracks which didn't have this permission in their manifest.json file. I did add the permission in current build but didn't have in other testing tracks i.e, open testing and internal testing tracks. So releasing the same build to all tracks did fix this warning instantly.

We need to send for review for google after you submit an AAB/APK?

Tasg: publishing to play console, publish to play console, publish

drawing

Google is now removing releases for any android version whose android version hasn't been released in last 1 year

image

Promoting Internal Testing release to Production release

image

Publishing to PlayStore Android

Article - Click here

Generating and submitting apk to playstore | Capacitor Docs

Clickh here

LEARNING OF THE BAD DAY Super learning about adding tester email to "Internal Testing"

Source: StackOverflow

It takes 3-4 hours or may be 1-2 days so that any new tester email added to tester-email-list to take into effect (before that it will show white screen when you try to browse the internal testing playstore link).