We are using Google Play Alpah testing tracks which can be tested by different testing teams for their respective modules.
But the links generated by these tracks are same how to get an application for a member which may be added to multiple closed alpha testing tracks.
e.g. We have two tracks Alpha Track 1 and Alpha Track 2, we have few common tester emails in these two but most of them get the apk from Alpha Track 1 which is the first created track. How can they install apk from Alpha Track 2 from their testing email accounts? Or do they need to have totally different email id for each track?
Google just updated their help center documentation regarding this. See Version codes & testing track statuses section (emphasis is mine):
Version code requirements
Users receive the version of the app that has:
The highest version code that’s compatible with their device, and
Been published to a track they're eligible to receive
All users are always eligible to receive the production track. If an APK with a higher version code is published in production than in the test track where the user opted in, the user will receive the production APK.
Users eligible to receive multiple tracks will receive the highest version code APK published on those tracks.
For a user to be eligible to receive a test track, the user must:
Be included in the managed track configuration, and
Have opted in to the corresponding test program
For example, all users who opted in to the test program are eligible for the open test track. Users who opted in to the internal test program are not eligible for the open and closed test tracks, even if they're included in the managed testers configuration. These users would not receive higher version code APKs published on those tracks.
For more information, learn about versioning your apps.
Hope this helps.
Related
I'm trying to release two different versions of my app on 2 different tracks:
- Open Beta Track
- Closed Alpha Track
However both tracks give me the same opt-in url https://play.google.com/apps/testing/com.myapp so both groups end up downloading the same version of the app.
How can I "force" the beta testers to only get those on the beta track and the other testers on the alpha track. I have used internal-app sharing and it works, the thing is that this is not automatic as with the tracks.
The URL is the same because opting in only means that they're eligible for receiving one non-production APK.
To determine which one they will receive, Play sends the user the APK with the highest versionCode they're eligible for (based on which test groups they belong to), which should in general be the furthest away from the prod track that they're eligible for.
Hope that helps,
Google Play supports various 'test tracks' to allow test builds to be distributed to different groups through the Google Play Store:
https://support.google.com/googleplay/android-developer/answer/3131213?hl=en
Google Play uses the application version number to decide which apk should be delivered to the user from the set of test tracks that the user qualifies for.
Given that an apk can be promoted to different test tracks, is it possible to detect (within the Android application) which test track was used to deliver the apk? For example, is it possible to know (within the Android application) that the application was delivered through an alpha test track or a beta test track?
The motivation behind this question is to enable different sets of features through a server-side configuration based on the test track an application was delivered through.
It's possible to manage this through version numbers alone but knowing which test track an application was delivered through would make this process easier.
I am working to publish a private, internal release for our app in the Google Play Store. I'm getting a message saying "An opt-in link will be available here when you publish your app", but I don't know what else I need to do publish my alpha test apk.
The release status says "full rollout", which indicates to me that everything is done.
I know it takes hours for it to appear but I already waited for days. What do I need to do to get this URL? If I sideload the apk that I created, will it be the same as downloading from the store (in terms of IAP authorisation)?
It's just a matter of time
Rolling out merely gets you to the Pending publication stage
After some time (say 45 minutes) you will reach the Published stage and the Opt-in URL
For many developers, it's just a matter of time. Rolling out merely gets you to the Pending publication stage. After some time you reach the Published stage and the URL will appear.
However, for your app, it looks like this app in unpublished. You can't opt-in to unpublished apps, so the opt-in link isn't shown.
For questions like this the Developer support team are usually really good, and we do have bugs sometimes, so it is always worth asking them.
When you create an internal test, you release your app immediately to your internal testers. This can help you identify issues and receive feedback earlier in your development process. An internal test is:
Fast: You can distribute apps via the internal test track much faster than the open or closed tracks. When you publish a new APK or app bundle to the internal test track, it will be available to testers within a few minutes.
Note: If you're publishing an app for the first time, it may take up to 48 hours for your app's internal test to be available.
Flexible: An internal test can be adjusted to support different testing stages, including internal testing, quality assurance checks, and post-launch debugging.
Safe: With the internal test track, your test app is distributed to users via the Play Store.
Be sure to check that you've completed all the required steps for publication! On the left sidebar of the Play Store for your app, check that there are no "!" icons; everything should have a green check-mark.
I have developed my app and have published it through Google Play for alpha testing. As one of the testers I get an opt-in link, where I signed in as a tester. After that I was hoping to download the app directly with my phone by going to the Play Store on my phone. But as it seems to turn out, I have to got to the app's web profile and then from there click download; only then does the Play Store download the app to my phone.
I want to get other alpha testers involved and I was hoping to make the process easier for them. Is there an easier way? As in, once they opt-in, I would like them to just use their Android phone to download the app the way they would any other app. Is there a way?
Clarifications:
I am not looking for an alternative to Google Play
I have already gone through the Google Group creation process. My question is concerning what happens after a group member opts-in. Can they use their phone directly (play-app on phone) or must they download from the website? So far I have not been successful using the play-app.
You need to publish the app before it becomes available for testing.
if you publish the app and the apk is only in "alpha testing" section
then it is NOT available to general public, only for activated testers in the alpha section.
EDIT:
One additional note: "normal" users will not find your app on Google Play, but also the activated tester can not find the application by using the search box.
Only the direct link to the application package will work. (only for the activated testers).
Here is a check list for you:
1) Is your app published? (Production APK is not required for publishing)
2) Did your alpha/beta testers "Accept invitation" to Google+ community or Google group?
3) Are your alpha/beta testers logged in their Google+ account?
4) Are your alpha/beta testers using your link from Google Play developer console? It has format like this: https://play.google.com/apps/testing/com.yourdomain.package
Publish your alpha apk by pressing the submit button.
Wait until it's published.
(e.g.: CURRENT APK published on Apr 28, 2015, 2:20:13AM)
Select Alpha testers - click Manage list of testers.
Share the link with your testers (by email).
(e.g.: https://play.google.com/apps/testing/uk.co.xxxxx.xxxxx)
It should be noted that releasing an alpha app for the first time may take up to a few hours before an opt-in link is available and invitations are sent out to the email addresses in your testers list.
From Google support:
After publishing an alpha/beta app for the first time, it may take a
few hours for your test link to be available to testers. If you
publish additional changes, they may take several hours to be
available for testers. [source]
You may want to wait until you have an initial opt-in link before publishing more changes to the app because doing so is likely to increase your wait time for receiving your tester link; or, may lead to your testers testing with the incorrect version.
Hope that clears things up for anyone confused about why they don't have an opt-in link as depicted in screenshots in this SO thread!
Under APK/ALPHA TESTING/MANAGE TESTERS you find:
Choose the method you want.
Then you need to first upload your Apk. Before it can be published you need to go to the usual steps in publishing which means: you need icons, the FSK ratings, screenshots etc.
After you added it you click on publish.
You find the link for your testers at:
Google play store provides closed testing track to test your application with a limited set of testers pre-defined in the tester's list known as Alpha Testing. Here are some important things to be considered to use alpha testing.
Important
After publishing an alpha/beta app for the first time, it may take a few hours for your test link to be available to testers. If you publish additional changes, they may take several hours to be available for testers
Managing Testers for Alpha Testing
The Screenshot is most recent as of answering this question. You can see the manage testers for closed alpha testing, You can add and remove tester one by one or you can use CSV file to bulk add and remove. The list of defined email addresses will be eligible for testing the app, here you can a control whom to provide the app for testing. Hence, this is known as Closed Testing.
You can see the link(washed out by red line), once your app available to test, your testers can download and test the app by going to the below-given link. For that Google will ask once to the tester for joining the testing program. Once they have joined the program, they will receive an app update. As stated by store, it may take 24 hours to make an app available for testing.
Once your app available, Your invited testers can join the test by going the link https://play.google.com/apps/testing/YOUR PACKAGE NAME
Managing App Releases
After the Manage testers card, there is a card for manage release, from here you can manage your alpha releases and roll-out them to production by clicking the button at the top of the card once they well tested. This process of rolling out from testing to production/public is known as stagged roll-out. In stagged roll-out, the publisher publishes by the percentage of users, to better analyze the user response.
You can also manage multiple alpha release app versions from here, at the bottom of the screenshot you can see that I have once more apk build version being served as alpha test app.
Managing Closed Track Testing Availability
Apart from the user based control, you have one more control over the availability of the app for a test in the country. You can add limited countries tester to the app. suppose your list of the testers are from multiple countries and you want the application to be tested in your country only, rather removing testers from the testing list, you can go through Alpha Country Availability. It gives more precise control over testers.
Here, In Screenshot, my app is available worldwide states that my testers (from testers list) can test the app in all countries.
In my experience the flow is:
you publish the app as beta in Google Play and create the Google+ community
invite the tester to the community
once he has joined, send him the link of the test app in Google Play
the tester opens the link in the browser (not google play app)
registers as tester
in the browser, install the apps to the device (the app will be magically pushed to the device)
Another issue of that page if you use multiple playstore accounts:
In some cases you still get a 404, even if you are currently logged in with the right account, the one you joined the beta community with.
As a workaround, you can clear the browser cache, use another browser for the beta signup, or just use the incognito mode of your browser.
You can use a Google Group and have your alpha testers just join the group. Everything else should just be handled through the Google Play Store App.
I have developed my app and have published it through Google Play for alpha testing. As one of the testers I get an opt-in link, where I signed in as a tester. After that I was hoping to download the app directly with my phone by going to the Play Store on my phone. But as it seems to turn out, I have to got to the app's web profile and then from there click download; only then does the Play Store download the app to my phone.
I want to get other alpha testers involved and I was hoping to make the process easier for them. Is there an easier way? As in, once they opt-in, I would like them to just use their Android phone to download the app the way they would any other app. Is there a way?
Clarifications:
I am not looking for an alternative to Google Play
I have already gone through the Google Group creation process. My question is concerning what happens after a group member opts-in. Can they use their phone directly (play-app on phone) or must they download from the website? So far I have not been successful using the play-app.
You need to publish the app before it becomes available for testing.
if you publish the app and the apk is only in "alpha testing" section
then it is NOT available to general public, only for activated testers in the alpha section.
EDIT:
One additional note: "normal" users will not find your app on Google Play, but also the activated tester can not find the application by using the search box.
Only the direct link to the application package will work. (only for the activated testers).
Here is a check list for you:
1) Is your app published? (Production APK is not required for publishing)
2) Did your alpha/beta testers "Accept invitation" to Google+ community or Google group?
3) Are your alpha/beta testers logged in their Google+ account?
4) Are your alpha/beta testers using your link from Google Play developer console? It has format like this: https://play.google.com/apps/testing/com.yourdomain.package
Publish your alpha apk by pressing the submit button.
Wait until it's published.
(e.g.: CURRENT APK published on Apr 28, 2015, 2:20:13AM)
Select Alpha testers - click Manage list of testers.
Share the link with your testers (by email).
(e.g.: https://play.google.com/apps/testing/uk.co.xxxxx.xxxxx)
It should be noted that releasing an alpha app for the first time may take up to a few hours before an opt-in link is available and invitations are sent out to the email addresses in your testers list.
From Google support:
After publishing an alpha/beta app for the first time, it may take a
few hours for your test link to be available to testers. If you
publish additional changes, they may take several hours to be
available for testers. [source]
You may want to wait until you have an initial opt-in link before publishing more changes to the app because doing so is likely to increase your wait time for receiving your tester link; or, may lead to your testers testing with the incorrect version.
Hope that clears things up for anyone confused about why they don't have an opt-in link as depicted in screenshots in this SO thread!
Under APK/ALPHA TESTING/MANAGE TESTERS you find:
Choose the method you want.
Then you need to first upload your Apk. Before it can be published you need to go to the usual steps in publishing which means: you need icons, the FSK ratings, screenshots etc.
After you added it you click on publish.
You find the link for your testers at:
Google play store provides closed testing track to test your application with a limited set of testers pre-defined in the tester's list known as Alpha Testing. Here are some important things to be considered to use alpha testing.
Important
After publishing an alpha/beta app for the first time, it may take a few hours for your test link to be available to testers. If you publish additional changes, they may take several hours to be available for testers
Managing Testers for Alpha Testing
The Screenshot is most recent as of answering this question. You can see the manage testers for closed alpha testing, You can add and remove tester one by one or you can use CSV file to bulk add and remove. The list of defined email addresses will be eligible for testing the app, here you can a control whom to provide the app for testing. Hence, this is known as Closed Testing.
You can see the link(washed out by red line), once your app available to test, your testers can download and test the app by going to the below-given link. For that Google will ask once to the tester for joining the testing program. Once they have joined the program, they will receive an app update. As stated by store, it may take 24 hours to make an app available for testing.
Once your app available, Your invited testers can join the test by going the link https://play.google.com/apps/testing/YOUR PACKAGE NAME
Managing App Releases
After the Manage testers card, there is a card for manage release, from here you can manage your alpha releases and roll-out them to production by clicking the button at the top of the card once they well tested. This process of rolling out from testing to production/public is known as stagged roll-out. In stagged roll-out, the publisher publishes by the percentage of users, to better analyze the user response.
You can also manage multiple alpha release app versions from here, at the bottom of the screenshot you can see that I have once more apk build version being served as alpha test app.
Managing Closed Track Testing Availability
Apart from the user based control, you have one more control over the availability of the app for a test in the country. You can add limited countries tester to the app. suppose your list of the testers are from multiple countries and you want the application to be tested in your country only, rather removing testers from the testing list, you can go through Alpha Country Availability. It gives more precise control over testers.
Here, In Screenshot, my app is available worldwide states that my testers (from testers list) can test the app in all countries.
In my experience the flow is:
you publish the app as beta in Google Play and create the Google+ community
invite the tester to the community
once he has joined, send him the link of the test app in Google Play
the tester opens the link in the browser (not google play app)
registers as tester
in the browser, install the apps to the device (the app will be magically pushed to the device)
Another issue of that page if you use multiple playstore accounts:
In some cases you still get a 404, even if you are currently logged in with the right account, the one you joined the beta community with.
As a workaround, you can clear the browser cache, use another browser for the beta signup, or just use the incognito mode of your browser.
You can use a Google Group and have your alpha testers just join the group. Everything else should just be handled through the Google Play Store App.