I have a published game in Google Play Game Service that links to a beta Android app. In Google Play Console I selected beta testing method as "Open Beta Testing". My problem is that the beta testers cannot sign in to Play Game. I tested with testers added to Play Game and it works fine. So it's not likely that I had integration mistake. I also enabled Alpha and Beta Tester groups under "Testing" of Play Game but no luck.
It seems that Play Game only supports Close Beta tester but not Open Beta testers.
Can any one confirm this ?
Been Googling around and found this documentation of Best Practices. It was stated that,
You can run a closed alpha and an open beta test on your app concurrently. If you run an open alpha test, you can't use the open or closed beta track. Keep in mind the version code rules when using different tracks.
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.
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.
If you just upload an app to your play developer account, then submitted it for BETA testing:
1 - Is the app actually published
2 - Is the app released on Play store
3 - Do the policies relating to Play Store published (released) apps still apply to BETA versions, bearing in mind its private usage only and the app is still in developement and not beed finalized.
1) Yes
2) Yes but it's only visible for people you've added to your beta group
3) Yes I believe so.
Otherwise you can upload it in alpha. Just few users (testers) could download it.
I am currently creating an android game using the Play Game Services for leader boards and achievements. I am currently testing the features under my account because I can clear the leader board when needed. However, I wanted to release an alpha test of my app. When I try to publish my game so my testers have access to it, it says I have to publish the Game Services first or they won't work. But, if I publish the game services can I still use testing accounts and change things? Or will it be final?
You don't need to "release" [edited] your game in order for testers to try out your game. One reason you may get the "I have to publish the Game Services first..." is because you most likely did not complete the Game Services and API setup between Google Play Developer Console and the app itself.
See steps:
https://developers.google.com/games/services/console/enabling#a_create_a_linked_application
Or, less likely, it could be that you still need to upload the APK:
Upload an Alpha or Beta APK, wait a few hours for it to become active in the system, and then add your tester group. This is a good place to start as of the date of my post:
https://support.google.com/googleplay/android-developer/answer/3131213
Some details from the link above:
Set up alpha/beta tests
Using the Google Play Developer Console, you can choose groups of users to beta test different versions of your app.
Testing basics
With the alpha/beta testing tools available in your Developer account, you can test different versions of your app.
You don't need a production APK to publish an alpha/beta app.
Users need a Google Account (#gmail.com) or a Google Apps account to join a test.
If you're testing an existing app that you've published before, only users in your test group will receive an update for your alpha/beta version. If you're testing a new app that you haven't published before, only users in your test group can find and download your app.
After publishing an alpha/beta APK 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.
If you make any changes to your app's Pricing & Distribution page, including setting your app price to Paid or Free, it affects your production, alpha, beta, and any future versions of your app.
Tip: When you're starting a new alpha/beta test, it's a good idea to start with a small group of alpha testers, then expand your test to a larger beta test group.
Definitely make sure to see more at the provided link:
https://support.google.com/googleplay/android-developer/answer/3131213