I created an Open Track Beta release a few days ago for the first time, which has shows up as published since yesterday on Google Play Console. However if I click the 'View on Google Play' button it returns 'Not Found' and when I follow the opt-in link, I get an error that it isn't available even though I'm logged in as the creator of the app:
I do have the option of releasing it to production, which I assume would work, but would prefer to have a working testing release first.
You need to add yourself as a tester, to test the app. So open beta channel click the Manage Testers and add the mail that you use as google play account at your phone.
But I suggest you use internal test channel for this. Beta is mostly used for the apps already released and it is open testing.
So open internal test channel, add your apk and add yourself as a tester by clicking Manage Testers and adding your email (the mail you use as google play store account at your phone), share yourself the opt-link which you got from internal test instead of beta.
Then you will have early access, so you can download it from play store easily
Related
This happens to all Google Play account (not testers only)
On Google Play Console it's already in the production release stage and all stages of the testing release are inactive
Make sure to deactivate your other tracks, and don't include them in your production.
Also, change your account and check if you are still able to see Internal Beta. If that's so, then remove your current account from internal testing from the play console.
If not then turn off internal testing and check again.
Before this, I found that my Internal App sharing was on "Anyone you share the link ...".
So it has to switch to "Restrict access to email lists"
I had an app that was in the Internal Testing phase, and I had added my own email to the internal testing list of testers. Now, I want to download the release on the Open Testing track, but when I visit my app listing on the play store, it still shows "(Early Access)" behind my app name.
I tried to follow the documentation for leaving a beta program, but there was no "Manage apps & devices" button when I clicked on the profile icon on the play store on my web browser.
So then I started up my AVD, opened up the Play Store and signed into my account, then I managed to find my app in "Manage apps & devices", but there was nothing there about leaving the beta program.
I also tried to remove the email list containing my email from the Internal Testing track, and then also paused the Internal Testing track, but I still see "(Early Access)" in the Play Store.
Then after more searching, I found this thread . I followed it and tried to add "/leave" at the end of my internal testing app URL, which worked (which already doesn't make sense since I already removed myself via the Google Play Console), but after clicking the leave button, I STILL SEE "(Early Access)" in the Play Store!
Must I create brand a new Google Account just to see the Open Testing of my own app??
(Edit: to clarify, I have not released my app to production yet. However, when I view the app on play store without logging in to a google account, I can see the Open Testing version, without "(Early Access)" behind the app name.)
I upload an app in Alpha testing for testing In app Billing, and I notice there is a button up to the right called Publish App, this means to publish my app in Production or to Alpha level?
Is this the reason why I get a message that says I need authentication to Google Play, when I click the Subscription button?
It depends on what tab you chose in the APK setup, if it's Production, Beta or Alpha. Follow this guide on How to upload and download an Alpha or Beta app to Google Play:
Sign in to your Google Play Developer Console.
Select an app.
On the left menu, click APK > Beta Testing or Alpha Testing.
Click Upload.
Select your APK file.
Click Publish.
For the error Need authentication to Google Play:
As indicated in this video, go to Google Play in your Applicaton Settings and click the CLEAR DATA button. Check this documentation about How to fix ''Google Play authentication is required'' error.
this means to publish my app in Production or to Alpha level?
When you upload to Alpha channel it gets published to alpha channel. You can later move the published apk to beta channel or production (if you want).
Is this the reason why I get a message that says I need authentication
to Google Play, when I click the Subscription button?
No, Which channel you upload to has nothing to do with the functionality. It is just to make the app available to specific set of people. Production channel will make it available for download to general public, where as the alpha and beta channel will make it available for download only to the users you'll add as testers for each channel. This is definitely not a reason that would impact functionality.
The authentication error must be a result of a problem either in your code or device. It has nothing to do with what channel you publish your app on
I need to test some features of my app like the "In App Billing" service so I published it in an Alpha version in Google Play, I filled all the required fields, I added the testers Gmail account, the app is signed and its version is higher than the Beta/Production version.
Since yesterday in the Alpha section of the Google Play Console I can see the app as published, but when I go to the Play Store the app doesn't appear, trying to get it from the provided link it says that the app isn't available because it has not been published or I can't access to it with my account.
I have verified the accounts signed up in the console and all is right, am I forgotting any step? Did I do anything wrong? Any help would be really appreciated, there is more than one day since the app is published and I cannot test it.
Thank you in advance
alpha applications are directly not accessible in play store you have to get link from developer account, where your apk is published there is link as manage testers click on that you will get link and only user who is member of that group can access it through registered email link will look like : https://play.google.com/apps/testing/uk.co.xxxxx.xxxxx)
https://support.google.com/googleplay/android-developer/answer/3131213?hl=en
For those of you who were installing Android TV app and had the same error as OP. Open your test link
https://play.google.com/apps/testing/{package}
on a desktop computer with account logged in on tv. Then you will be asked to participate in tests, and after acception you will be redirected to your alpha google play website. From here (on desktop pc) you can install it on your TV.
We missed the "Choose a testing method" step inside the APK menu option, thank you very much
So I've went through all the steps to upload my .apk to the Google dev console, and I've added my Google group for the list of people that will be testing it. Then it asked me to publish my app so I can get the opt- in link to send to my testers. I'm supposed to be able to send out a non production ready app to beta testers, but when I try to set up the beta channel, it wants me to publish my app and wants it to be production ready. Can anybody walk me through the steps of setting up my beta app so I can get the opt in link to send to my Google group?
Just upload your Beta into the Beta channel. You actually have to publish the app. This only publishes the Beta for your testers, not a production channel.
So the steps usually are:
upload apk into Beta
paste the link to your community/Google group
publish the app (top right corner)
grab the opt-in link and send it to your testers
send a Play Store link or the signed apk to your testers
This takes like 2-24 hours for your testers to see the app in the Play Store. Some of my testers still don't see the app after 4 days.. Seems not completely reliable, yet.
Hope this helps. Have fun :)