Logo Questions Linux Laravel Mysql Ubuntu Git Menu
 

Google Play Alpha and Beta testing APK version

I'm trying to use the Alpha and Beta testing mechanism in Google Play Console, my question is: Are versionCodes of APKs in Alpha and PROD related? meaning if I upload an APK with versionCode 9 to Alpha, do I have to continue in PROD with versionCode of 10? or can I upload to PROD versionCode of 6?

like image 963
Omar Avatar asked Jul 31 '14 22:07

Omar


People also ask

What is alpha version of an app?

alpha version (plural alpha versions) (computing, technology) An early version of a program or application, typically unstable, but useful to show what the product will do. Sometimes this stage is referred to as a preview version. Sometimes no more features are added after this release, but bug fixes continue.

What is alpha and beta testing Play store?

An alpha testing group should be small and test the least stable, experimental versions of your Actions (such as within your company or team). Use beta testing with a larger group to test stable versions of your Actions that are near release. Provide a channel for testers to send you feedback.

How do internal testers get the app Google Play?

When you publish a new Android App Bundle to the internal test track, it will be available to testers within minutes. Note: If you're publishing an app for the first time, it will be immediately available to internal testers, but will have a temporary name and store listing information for up to 48 hours.


1 Answers

yes they are related. Version codes should always be bigger than the .apk you uploaded before.

for example:

  • current Production is 9
  • to upload an Alpha it must be 10
  • then you upload a new one to alpha it must be 11
  • then you migrate it to beta.
  • then you upload a new beta it must be 12
  • then you finalise some details and going to upload to production it must be 13

but remember that version codes are different than version names. codes are usually not user visible. Names are. So you can still make it look like a normal upgrade path to the production users.

for example:

  • production 9 is named v1.0.5
  • then production 13 will be named v1.0.6

and all the others you called v1.0.6.ALPHA1, v1.0.6.ALPHA2, v1.0.6.BETA1, v1.0.6.BETA2

like image 60
Budius Avatar answered Oct 04 '22 14:10

Budius