Game store Beta Testing returns 404

Question

I’m a developer, and I was delighted to watch Google IO 2013 and learn about the new beta testing feature. So I created a Google+ community and a google group and posted testers there (including me).

All we get (developers and testers) when we visit https://play.google.com/apps/testing/com.package.stuff is:

Is there a trick I don't see? I would really like to use this feature.

I know that there are alternatives such as https://testflightapp.com/ , but I would prefer to keep my application in this environment, where I can "push" the beta version of apk to the production phase, etc.

Answer 1

I had the same problem. The reason the link doesn't work is because the app needs to be published before the link is active. I repeat, the application must be published, this does not mean that the APK should be in production. At the top right of the page of the application developer console there is a drop-down menu that allows you to publish the application. This link will immediately take effect, and your application will be available in a few hours for your testers in the Play Store.

Answer 2

First of all, you need to create a Google+ community.

Process:

• Create a new Google+ community. It must have testers through the developer console.
• Register this community on the Google Play Developer Console
• Invite your beta testers to this community.
• Wait 8-24 hours before using the link.
• Share the link with your testers
• Make sure your application is published for beta testing.

If everything is correct, the link should show something like:

Answer 3

2015, and alpha beta testing at best - 50%. About 50% (23 of our 60+) beta testers never access the application using the link provided. Everyone else has no problem installing the beta application and getting updates. No rhyme or reason. A single account on your device, and some with Gmail accounts, and some with private email. This is a mixed bag that gets access and who doesn't. In all cases, when they accept the invitation to join the group, they have full access to the group. But they get 404 when they try to access the application. No problem. Our solution is to give testers access to our private server and thus transfer beta versions. Updates are not automatic, but testers can get a free application

Answer 4

I have the same problem, the link just does not work, 36 hours after publication. I may not even provide alpha / beta features if they cripple the developer’s ability to move quickly ...

In any case, I am sharing the information provided to me by Google support, hoping that it will be useful:

• Make sure you add a valid Google Group URL or Google+ Community URL to the Developer Console and that you are included in the group / community. After adding a group / community, the group name will be displayed in the "Manage tester list" link on the testing tab. (Please note that when adding a Google group, you need to enter an email address, not a URL).

• If you want to use the Google group in the Google Apps domain, the Developer Console and the private channel must be enabled for your domain in the Google Apps control panel. Read more Private Channel: http://goo.gl/DLGNe

• The application must be published within a few hours before the link to access will be available to testers.

• Currently, testers must have only one account on their device. Devices with more than one account will receive a production version of your application. (Please note that this requirement is temporary. Stay tuned).

Answer 5

I had the same problem and the alpha tester had to get into my Google Plus community for alpha testers.

Answer 6

I had the same problem (error 404 on the tester link), but the reason was different from that shown in the answer of buckson18: in my case, the application was published, but the user did not join the Google Group tester, although he received an invitation. After the user joined the group, the page showed correctly.

Hope this can help someone ...

Answer 7

I also ran into this problem. The problem was that the Google group was not added. Another important thing to take care of is that the account used for the developer console must be included in the google group. I could not find it anywhere in the documentation.

Answer 8

I solved this by going to https://play.google.com/apps/testing/[app package] on the device, and then click this link and open it with google play

Answer 9

I have been using beta testing for several years and am very unreliable. Sometimes it works, sometimes it doesn’t. Now they have Open Beta Testing. I tried it for the first time today, and although I followed all the instructions, it still doesn’t show the application in the application store unless I enter it, which makes it a normal old-style beta testing. Its much simpler and no problem to use HockeyApp to distribute a testing application.

Having lost a watch with Goolge Alpha and Beta versions, I always add my application to production so that I can store my testers. It is already difficult to convince a large number of people to do testing, and then continue to ask them to complete half the work or not work to download the application.

Answer 10

One thing that seems to work for us is to use the "Access URL" that the Play Store Developer Console provides in the "Applications" section, which should look like this:

https://play.google.com/apps/testing/com.yourappname.android

This is DIMENSIONS than the URL that you see if you are already approved as a tester and visit the application page in the Play Store in a browser. Ours look like this:

https://play.google.com/store/apps/details?id=com.yourappname.android

Clean network, use 1st, not 2nd. Good luck

Answer 11

It should also be noted that the link is case sensitive, so if you have https://play.google.com/apps/testing/com.someAppName - if you added https://play.google.com/apps/Testing/ com.someappname, it will tell you that it is unavailable!