I posted a new beta version in google developer console, but device doesn't see new available beta version. It has been more than 3 days since I released. May be the reason that the application has been installed to the computer, not downloaded from google?
when you upload an Alpha Testing apk, it doesn't appear in google play as production app. What I've done is to create a community in google+ and then I associate that community to my app. Here I show you where you can do it:
and
If you dont want to create a community like me, you can also add the gmail of the "testers" that you want to test your alpha/beta app. Don't forget to add your own email ;).
Hope this help you.
Related
I have been trying for several weeks now to get the Google Alpha / Beta testing functionality on the Play Store to work with no success. As far as I can tell I have followed the process but clearly something is not working from my side. I hope someone on SO can tell me what I'm doing wrong.
I have created both an Apha and Beta testing community.
I have added the Beta testing community to the Beta testing section that relates to using Google+ communities to test. My Beta testing community does have members added.
Although I have an Alpha testing community, none of the Alpha testing methods are currently enabled.
On my test device, using a Google account that is a member of my Beta testing community, I only ever see the version of my app that is currently in Prod. I have spent days waiting just in case it takes a couple of days to show up (at least a week which I assume should be long enough).
I need to test the release version because I am trying to test some inapp billing functionality that I had to change due to security warnings from Google relating to my current Prod version.
BUT: if I load the release version of the app directly (instead of downloading from the Play Store) I can see that it is seeing this account as a "test account" because when I test the inapp billing I get the correct message telling me that the subscription will renew every day but I won't be charged. However the Beta version of the app never appears in the "BETA" tab in the Play Store.
I have noticed something "strange" (possibly) in the developer console though: When I click on the "Beta Testing" tab it shows 10399 supported devices and 0 excluded devices for the Beta app. However if I click on the line of the Beta app where you can promote the app etc, the details that are then displayed indicate 0 supported Android devices. Why would this be? This seems to be conflicting information on the console.
Note: The current Prod version of my app was developed using Eclipse. I have recently converted to Android Studio and this is my first upload using Android Studio.
Where else should I be looking to get my app to appear in the Play Store
Thanks
I was just setting up the Beta testing release for the first time and couldn't make the app visible in Play Store. Found the reason in Play Console Help:
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.
After about 35 minutes the app was published.
As this might not be the issue mentioned in original question, it might help someone.
In my case I had published the Beta version and had created the testers but not linked them together. What I had to do was:
Go to manage releases
Choose a testing method - Closed Beta Testing
Then when testers list shows, make active the group of testers you would like to test the app.
Save
Get Opt-in URL link and paste it in a new tab (you should be logged in to google)
Then click at the "Become a Tester" button
You should now be a tester and ready to go.
#Important If you still can not find the app by searching in Play Store just copy the "Opt-in URL" into your tester phone's browser and you should see the app.
Hope it helps
What solved this problem for me was clearing my Play Store app data.
In my case, I had already been on the testers list for days, already accepted the invitation link, and already gotten testing working on other devices. But, the Play Store still wouldn't show the beta version of the app on this particular device.
I went to "App info" for the Google Play Store app, "Memory", then "Clear data". Then I re-opened and was able to see the beta test app.
Disclaimer: Use with caution. Clearing your app data may remove some important information. I haven't personally experienced any problems with it, but that doesn't mean you won't.
The suggestion from #Edgehog to use Open Testing solved my problem regarding being able to see my app in the Beta tab of the Play Store.
I have not found a reason yet why the closed beta testing (using emails or groups/communities) would not work.
Make sure you also check this answer
browser cache
an actual active "testing track"
We are having the same problem in my company. Currently we are investigating possibility that maybe first install on beta channel installs prod version and updates to beta channel version when first app update is released on beta channel. It is weird workflow but the comment on Play Store "Future updates will include beta versions" supports this
There are a couple of reasons why this might happen but admittedly we did not 100% confirm this.
1) One reason is that you are viewing Google Play under another account that is not on the beta tester list.
2) The other might be an issue (or feature) with the release management. Added a user to an existing closed beta release list. Changing a list does not activate or force a Save for the "Managed testers" section. After we edited another field (e.g. feedback channel) then the Save button became active and we clicked save. This might only then propagate changes. We cannot 100% confirm this was the issue we were facing but our experience points to this.
This may be a dumb question, but I do not want to waste my time creating an app and then finding out I have to wait till Android Studios 2.2 officially comes out. I want to download and start using Android Studios 2.2 and use the new constraints layout they added, but it if not officially out. Does anyone know if apps created in Android 2.2 can be submitted to the Google Play Store?
Well of course you can.
I don't see any reason why you shouldn't be able to. All you need to upload an App to the Play Store would be your GMail Account, A Google Developer Account (with your GMail account), and then you can upload your APK using the Developer Console. I am not updated to the specific details you have to fill out but I'm pretty sure that as long as you have a good APK file (that isn't violating any privacy rules) then I think you're good to go.
I want to send the application to the beta testing Google Play. My question is: how to do in the application so that at the end of testing people could update the app and enjoy working version. How to organize it will be in the API and in the application? Share your experiences, links or something else. thank you
There's nothing to do within the application or over some API. Right in the Developer console you're given the ability to promote your uploaded version to the Beta or Production stage. See the following screenshot:
So as soon as your app is ready for the masses, just push it to Prod and everyone will be able to download and/or update it.
How to publish beta test-version in Android play store ?
I'm trying to allow beta test my phonegap build app in the android play store. I already uploaded a signed apk in the beta tab and added a google+ group with some users inside ... but I'm slightly surprised that I cannot find how to install or even find this app on the testers smartphones. I opted myself as user in the group but cant see a link to the app or something like that. Shouldn't the app be already visible to beta users in the app store? Or do I have to push the publish button? The info popup tells:
"Your app can only be used by your testers when it is published to Google Play.
If your app has no production APK then it will only be visible to Alpha and Beta
testers. The link that your testers can use to opt-in will be displayed here when
you have published your app."
Sounds to me that it should be published. But doesn't it mean that the beta apk will be moved to the published-area and not being then a beta any more? I'm afraid that the app will be then visible to all users in the play store not only for my beta testers.
Could someone explain me how to publish a beta for my testers only?
EDIT:
It seems that everything I need is the opt-in link that is missing. Any idea why?
In order to be able to get the link to share with your group you have to first press the "Publish" button in the upper right. After doing this you will see the link to share with users appear as brheal shows above.
I'm adding this graphic to the discussion to help clarify exactly which one to press and which to not press.
Per the discussion above I was still a bit worried about pressing the publish button. I just did it and it works.
For more clarity I thought I'd share what it looks like. After publishing your beta apk you have to wait up to 24 hours (it took mine about 12) and then go to 'Manage list of testers' in your 'Beta Testing' tab. When it's ready you will see the opt in link available to share:
This is really an issue Google should address ASAP. You enter the console hoping to find the sections but the documentation says something else altogether. I just solved this and found the link, here are the steps updated with the current UI of the console which is not matching the documentation:
Open Google Play Console
Open your app
In the left panel go to Release management -> App releases
Scroll down to Open track, Closed track or Internal test track section according to your case, click Manage
Go to the section Manage testers and click Internal test
At the bottom you will see the link if everything is properly configured and the app is published.
VERY IMPORTANT
You need to configure the internal test list, I assume that if you
are looking for the link you've already done this.
The app needs to be published, remember it takes some hours, otherwise you won´t be able to see the link.
Here are the screenshots:
Not enough points to comment, hence a separate answer.
My suggestion is to upload a new build after setting up the beta testing.
I created a new app and rolled out the Beta version of the app.
After that I enabled the "Closed Beta testing" for a list of users - alas no opt-in link was ever generated.
After scratching my head a bit I released a NEW build which generated the opt-in link immediately.
I figured that enabling the "Closed Beta testing" AFTER the Beta version was released could have caused the issue and is maybe why the UI is constructed the way it is.... just a guess.
Try and release a new build.
How do I upload the beta version of the app .. In developer console we have 3 categories to upload , one Alpha testing and second is Beta testing and 3rd is production I have to publish beta version of the app. what should I do? Should I go to upload APK in Beta segment and promote that to APK or something else please remember I am asking about the beta release of the APP not beta testing?
Apps that are published as Beta are not listed in the Play-Store!
If you want someone to test it, you need to invite them (via G+) and send them an Opt-In-Link.
If you want to promote your App, just publish it normally and mention that it´s still in Beta.
EDIT: You can still promote an App that is in Beta to "normal" (production I think), no need to reupload or anything.
The previous reply is a little bit outdated (10 years), so here's an updated information:
see here for early access release:
Playstore : How to release early access app?
and here the direct information from the Google:
https://developers.google.com/assistant/console/releases?hl=en
Basically you have these options:
Draft
Alpha - only users who knows about the app, no review required
Beta - early access, requires review
Production - before review
Released/To-be-fixed - after review
Here is the scheme from the Google page: