I have an app that previously had a beta release that was promoted to production. The version code of this app was 1.3.x (y)
We updated the app and updated the version and we created an alpha release with the new apk. The version code of this app is 1.4.x (y+1). We have given ourselves invites for the alpha track.
Although the documentation and the forums say that if an account is eligible for both beta & alpha he will receive the alpha version, I can see this doesn't work in my case.
The link for opt-in is the same for both alpha & beta, and when I enter with an account eligible for both, it takes me to the 1.3.x(y) beta app, instead of the one from alpha.
About 4 hours passed and alpha usually is distributed instantly, so I don't know what the problem might be.
As far as I can see, the link sends to the beta app, not the alpha one. If I add a person only to the alpha program and go to the app on that account or to the link https://play.google.com/apps/testing/com.package.name it says I am not allowed.
Related
I have uploaded a new version to the closed Alpha track in play store, added testers and published. I have gotten the opt-in URL and have joined as a tester. Everything seems fine until I go to the app in play store. Here only the old Beta version is available and I cannot find any traces of Alpha anywhere. The app has been published in aprox. 12 hours when writing this. I have not received any mail or notification yet.
I have used the open Beta track a lot before and never had problems with this (did not need to wait for long before it was available). Do I need to wait even more, disable Beta or do something else?
Note: Alpha and Beta have the same opt-in URL...
I've experienced the same, on the playstore app it shows you the "highest level" you have access to. So if you are in the alpha & the beta it'll show you the beta.
Therefore remove the invite to the Beta version, and they should be able to see the alpha version.
Note that this is in the playstore app, from the web you can direct link to each track.
I have an application in the play store and I want to set up a beta track and an alpha track. In short, the beta track is intended to be open so people can opt-in anytime, while the alpha track is intended for select invitations only.
One of the problems that I'm having is that the beta-track seems to be recognized on my phone but the alpha track weirdly is not. The alpha track has a higher release version than the beta track has, so I am expecting the play store to show list the version of the alpha track (on my personal devices) however it quite persistently keeps showing the version of the beta track.
Anybody know what this is about? Am I using the playstore wrong is there something else I should enable first?
Your understanding for the play store is a bit different. Its better to look at the channels as below:
Alpha Track as Closed Track. Only registered users can install the app in this track.
Beta Track is Open Track. Everyone who has opted for Beta testing can install the app.
Production Track is your main track. Play store will use this to distribute your app to your end users.
To register your users for the Closed Track(Alpha), go to the Alpha track and add a list of users by their emails who can download app through this channel. My company uses Developers who can access the Closed track, so simply add all the developer's emails in that list and you are good to go.
Firstly you have to register alpha testing group for your app. If you register both alpha and beta testing groups, your project's version code is important. You are going to see the biggest version code number app in your phone alpha, beta or production. For example you have an apk in beta with version code 3 and you have an apk with version code 4 in alpha, you should see alpha version available on google play.I mean that the important thing is version code of your app.
I have an Android app on Google play store with alpha and beta testers (in addition to production) and so far everything was working well.
I am trying to add a new user to the closed beta testing list on google play store. This user is already using the app on production.
For some reason, although his email address is in the beta testing list, he cannot see and download the version that is published to beta. (Only the version on production).
Any reason for that or a way to fix this?
Edit:
I continue to experience this problem: Once a user have already downloaded the app on production, he cannot become a beta tester. Does that make sense?
After chatting with a Google Play representative, I have finally solved the mystery:
First, a user must uninstall the production app and only then he will be able to see and download the alpha/beta version through the Play Store. (He must also follow the invitation link of course).
Second, surprisingly, when you promote a version from alpha to beta - alpha testers can no longer download this version. More precisely, according to the representative -
"When you promote to beta the testers need to opt-out of the alpha test using the same opt-in link, then uninstall the app from their device, and wait 24 hours"
This in some of the cases was my problem since I assumed alpha testers can still have access to the new app version after it is promoted to beta.
There is a way to have both production and beta versions.
You need a fresh beta release, which means its build code should be higher than your production release.
You need to invite/add the beta testers, ask them to follow the link to take part in the testing etc.
The beta testers need to wait few hours for the beta release to roll up. Probably also have to remove the production version.
What are the differences between beta, alpha and production ?
It is possible to move from alpha or beta to production ?
You can upload an apk production and hide ?
What are the differences between beta, alpha and production ?
beta and alpha are testing channels which is not available to public on playstore app. The apps under these channel are available only to your testers.
Alpha testing group users are eligible for the alpha, beta, or
production version of your app with the highest version code that is
compatible with their device. Beta testing group users are only
eligible for the beta or production version of your app with the
highest version code that is compatible with their device.
apps in production are available to anyone who uses comes to playstore (provided you've chosen to distribute in the user's region) production
Read this Google help page for a detailed overview of each.
It is possible to move from alpha or beta to production ?
Yes, you will get a direct upload to do that against each apk in alpha/beta. Tou can also move directly from alpha to production (skipping beta) if you want.
You can upload an apk production and hide ?
No, once in production is there. You can only update it or unpublish it. Unpublishing is like hiding. (if that is what you meant - you can later republish it.) But, then you wont be able to also publish alpha or beta i guess.
If a Google Play tester is added to the alpha and the beta channels, they will (correctly) see whatever version is newest. So they'll see the alpha build if there is one available and the beta one if not.
However, if they start as a beta tester and are added to a group in the alpha channel, it doesn't seem to work. They still only see beta channel versions no matter if they leave the test, uninstall, etc.
What needs to be reset or changed so that a previous 'beta only' user can correctly be in the alpha and beta channels?