We want to start using google play for testing (We used Firebase until now).
One of our tests is version upgrade (from the current production version on google play to the new production version which we want to publish to google play), but we can't figure out how to do this - in google play.
When internal tester opens the test link, he always see the internal version.
The test page at the bottom has the option to 'Install the public version on Google Play', however, clicking on that link, opens the internal version.
The way we deal with that right now is by having two google accounts on a device, and only one of them is for the internal tester.
In this way, the other account still sees the current production version.
Is there a way for internal tester to view the production version?
There are two possible solutions:
The tester would have to leave the internal testing program by clicking the "Leave the Program" button above. They would then see the Production version
The other way would be to put the Production version in both your channels - Internal Testing and Production
Related
I currently use the inner sharing of the play console to release new versions to testers. (They have exactly the same package name and signing key.)
However, the testers responded that they could not upgrade from the official version to the test version, so the app update process could not be tested.
If I install the app first and open the inner sharing link, the play store displays
"A public version of this app is already installed on this device. Uninstall it and try again"
Is there a way to upgrade directly from the official version to the test version in the play store like installing an apk? (not uninstall app)
For example, the internal test of the play console may be possible?
Thanks for your help.
If you're using internal app sharing https://play.google.com/console/u/0/internal-app-sharing/ to share your app, then it won't work. Internal app sharing is used to quickly share an app with your internal team and testers, it doesn't undergo google play review process.
So you can't update your public version using this.
You can however, use different play console tracks for uploading your apps and they will support updates. Here https://support.google.com/googleplay/android-developer/answer/9845334?hl=en is the link for setting up open closed or internal track. When you upload your app to any of these tracks, they'll go through the google review process and once the app is available on playstore, testers can easily update it.
In case you don't want to wait for review, and want to use internal-app-sharing only, then, you can create 2 different versions of your app(different version numbers) and upload both of them to internal-app-sharing. You can then share the 2 links to your testers, and your testers should first install the lower version app and then open up the link of higher version number apk. It'll show the update button.
Edited(Thanks to #pierre): Although it looks like you're uploading artifacts signed with the same key, the Play Console actually re-signs the artifacts in the internal-app-sharing to avoid distributing an app signed with the production key that hasn't gone through their review process.
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.
We're currently using the public Beta feature of the Google Play Developer console alongside a live released app (though only in one country so far).
For both, we only have one link to the Play Store. If you are located in the country where it is live released, you get the live version - otherwise you get the beta version.
But how can we allow people in live released countries to access our beta app?
In Play Console there's a "Opt-in URL" value when you go to App Releases/Manage Beta/Manage Testers ....a user with live version of app that clicks that link (and agrees to be tester) will get the beta version of the 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.
I've pushed a beta version of my app to the play store and am now trying to see it in the play store on my device. It's not showing up.
How can I tell whether it has been published?
When I go to the play store on my laptop and search for my app, only the production version shows. If I click on the search result, it goes to the app store page with a warning "you don't have any devices". That part is fine. But should the search results also show my beta version?
I've set up a google group of which I'm a member.
I'm assuming that if the play store shows it on my laptop and doesn't show it on my device, then I have some sort of configuration problem - that is what I'm trying to debug in the first place. However, without knowing if the beta version is published, I'm in the dark.
Any one know how to deal with this situation?
The best way to verify that the Beta app is installed on your device is to actually install the app on your device from the Google Play store using the account with which you have opted-in to the Beta Test group. You can then verify that the Version Code of the Apk is indeed the Version Code of the BETA Apk that you have uploaded. You might want to print the version code to logcat as your app stats so that you can verify it easily. You can then also opt-out of the BETA test and reinstall the app through the Play Store and verify that it is NOT the Beta Apk by once again looking for the version code.
The Play Store now allows open and closed beta testing, although this was not always the case. If your application is in open beta testing, then it should be in the search results, given you've got a version in production. (I'm lead to believe that if your app is in open beta but you don't have a production version, it will not be in the search results).
In order to test to see if your application is available in the search results, you must disassociate yourself with your developer Google account to do your search. This will remove the association that your Google account has already with the application. It sounds like you've done that "on your laptop" since it says you say it says you have no devices. If your computer is logged into Google, you'll need to open a private browsing window or log out of that Google account, then do your search. If the search returns no results, the application will not be discovered by new users. But those same new users could still be in the beta by using the beta link that you have the option of distributing.