This question already has answers here:
Google play, I accidentally uploaded production APK, now can't do beta testing
(3 answers)
Closed 5 years ago.
My android app is live on Google Play. The latest version is 22. I had not used alpha and beta testing so far. Now App Owner said that Unpublish app from app store So that nobody that can view app any platform PC, mobile etc.
He said only selective people can view this app. So I decided Alpha testing using Google plus community. But problem is that if I unpublish app, Link of Alpha testing is not showing the app in play store for newly added users in the community even they become the tester. It's only working Users who have downloaded the app. If I republish app then it is working for ALL.
So my main question is How does Alpha testing possible for new users of google plus community without publishing App?
If you read the Publish documentation carefully, you will find that the version code of Alpha should always be greater than beta, and beta version code should always be greater than production.
i.e
alphaVC > betaVC > productionVC
the alpha version always remains higher, you cannot put a lower version apk.
The flow of testing is, fist rollout in alpha, then move same out to beta and then same one to production, on passing of consequent tests and approvals.
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'd previously uploaded a beta app whose version code was 660000 (addressing a bug fix). If I want to push out a new beta version whose version code is lower than 660000, I can't do it, which I understand.
Now, I'd like to deactivate/remove the 660000 version from app store so that I can publish my new app. How do I do that? Documentation on google playstore is more or less not helpful in answering the question.
You can deactivate the current app in beta by pushing/uploading a new version of the app for beta release with version 660001 or higher. Another option is by promoting app in alpha to beta. if you have an alpha app you can promote the same to beta, which will also remove the current app (only if the version if the incoming from alpha higher than the existing one). I hope it solves your issue.
We recently decided to update our new application for Beta release on google play,
Now after reading the guide, there were some questions that I had in my mind and wanted to know more about them, I googled for further understanding found some answers but there are still somethings that I wasn't sure about so decided to put this question up:
For Beta releases is it possible to make a beta release that is available to all the google play users(as a normal production app) or will it be available to all?
(Since as per this guide it gives me an idea that the application will only be available to a set amount of users.)
Make sure users can join the tests. Your testers will need to have a Google account (#gmail.com) or a G Suite account to join a test.
Run tests internally. Use the internal testing track to push your app to up to 100 internal testers in seconds.
Once I release a beta application and I decide to now put it for production, will it be uploaded as a different application or the same also will the comments that were posted to the beta release google play app be visible on my production app?
(Didn't quite get anything in relation to this one.)
In one of the points, it said that my application should have a higher version code in the beta release then that of the production release, But if I have a higher version in that release would it not be the application that will be getting downloaded even when it might not be the most stable version? (this one actually confused me big time)
Check your Android App Bundle version number. For an app on the internal, closed, or open testing tracks to be available to testers, it must have a higher version code than your production version.
Is there a designated field where I can provide this email for the beta testers or can I just provide it in the description of the application?
Provide a channel for testers to send you feedback. For closed tests, offer testers the ability to provide feedback by email, at a website, in a message forum, or through another suitable mechanism.
For Beta releases is it possible to make a beta release that is available to all the google play users
You can release your app as an Open Beta, which anyone who wants can get access to (without being invited by you). See https://support.google.com/googleplay/android-developer/answer/3131213?hl=en (specifically the part Step 1: Set up test details - Open test: surface your test app on Google Play)
Once I release a beta application and I decide to now put it for production, will it be uploaded as a different application or the same
Same. There's no re-uploading - you just change the state of the release.
also will the comments that were posted to the beta release google play app be visible on my production app?
Testers can't leave public reviews on Google Play.
But if I have a higher version in that release would it not be the application that will be getting downloaded even when it might not be the most stable version?
Well, that's the point.They have opted in to be testers of your app, so they get the latest available version. If they want to revert back to only getting production versions they can opt out of the test program.
Is there a designated field where I can provide this email for the beta testers or can I just provide it in the description of the application?
This is explained on the page I linked to: Next to "Feedback channel," add an email address or URL to collect feedback from testers. Your app's feedback channel will be shown to users on your tester opt-in page.
Beta releases are just a different track on your app's page.
If you have a public beta program (you'll need to select that as your type), users will see a "Join Beta Program" card somewhere on your app's Play Store page when they visit it. This card should show up below the "Developer Contact" information.
If a user decides to join the beta program, they'll get any new versions you publish there just like a normal update. Beta users cannot leave reviews! Beta users can leave you, the developer, private comments, but unless they leave the beta program, they can't create a review or edit an existing one.
Once you promote your beta build to production, it'll be available to all users of your app as a normal update. Beta users won't receive an update, since they're already on the version you promoted, nor will they be pushed out of the beta program. If you upload an APK straight to production, beta users will receive it as well (they still won't be able to leave a review).
As for version numbers, you can't upload another APK to the Play Console unless it has a later version code than the latest one already uploaded. If you have version 7 in your production channel, you can't upload a new APK with version 7 to beta; it has to be version 8.
When you upload your app as a Beta version, The users who joined your beta testing can upgrade to that version. The other users who have not joined beta testing, will no see any update for your app.
When you want to make the beta version as a production release, you can do so by simply clicking on Promote to Production option on Google Play Store.
With concern to your confusion, when you have some apk in beta version (say versionCode 2), then you can promote that app as a production, or you can also upload another apk as a production but remember, that should have greater version code (say 3). If you do so, then all users will get that update including beta testers. That will be an update to the same app.(I think you're doubtful here) Hope this helps.
I believe this question would be a repeat of this question:
Android in-app products not appearing in Play Store or app
but that question does not answer my question clear enough, so I'm asking again.
I have an app that I would like to test the in app payment feature, and I have read that in app products will only be available once the app has been published to at least beta or alpha.
I want to publish the app to beta or alpha, but it seems like in order to get a opt-in URL, you need at least one version of the app released to the public(playstore), if I am not wrong, and I do not want to do this as the app is still in development.
Is there a way to do a alpha testing before releasing no versions of the app to the playstore?
Here is a screen shot of my google play console:
Edited:
Why am I not seeing a opt-in URL here?
So it turns out that it takes like 2, 3 days until the alpha or beta testing goes live. The official documentation does not say anything about it, and it actually makes it sound like it happens instantly.
You'll receive an update to the for your app if you already have it installed on your device.
If you don't have your app installed, download it on Google Play.
Note: It can take a while for you to receive the update.
You can leave the testing program at any time. You can switch to the public version of the app if that's available.
To switch to the public version:
Uninstall the testing version.
Install the public version on Google Play.
Note: It can take up to a few hours before you can download the app's public version.
For current version Of Google Play Console:
Release > Testing > Closed Testing > Alpha
1. Click On Testing (Option Under Release)
2. Select Closed Testing.
3. Select Alpha Track.
4. Upload Your app Bundle or Apk.
Follow these steps on your Console:
1) Complete store listing, pricing & distribution, content rating
2) Upload your apk and release to alpha
3) Complete in-app products (Requires billing permission from manifest)
4) By opt-in url you can test the application
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.