I created my first Android app and wanted to let some users take part at the new Google beta testing feature. Unfortunately my app got published as a production APK and is visible to everyone now. That was not my intention, because my app is far from being released.
If I unpublish my app it also get's inaccessible for the beta testing users. So I have to keep it published to run the beta test.
What are my possibilities to make the best of this situation?
Using a dummy app as production APK?
Keep it unpublished and start with a new package name all over again?
Easiest way would be to delete the published app, but Google says NO.
You can put your Google Play Developer Console into "Advanced Mode" by clicking the button in the top right corner. Then you can activate/deactivate APKs as necessary, and upload APKs specifically for beta testers only. You do not need to change the package name.
After filling in all the details, In your developer console dont upload your APK to the production tab, only upload it in the Beta tab and click publish. Now wait for it to get published and find the playstore link which you can find after clicking the "Manage list of testers" link which is under the "Beta testers". Share this link with your beta users.
Even I made similar mistake before and then unpublished my app. Started again the publish process with different package name as Google remembers your app by the package definition. You won't be able to delete an unpublished app. That needs to be unique. When you create your app, don't upload the apk first, just prepare store listing. Once done, you will see all the panes, production, beta, alpha under APK menu. hope this helps.
Provided the constraints you have, I guess your best option is to set the filter of the APK to no devices if allowed; if not, set it to a single device (one you figure there are almost none in the market).
Additionally, you can change your publishing options for no country (or, again, to a single small country), although I think that might impact the beta testers as well...
I've just found myself in a similar situation (app was published to production prematurely, and I need to do some beta testing). Jorge's answer got me thinking. I found an option under "Pricing and Distribution" which allowed me to restrict distribution to my organization.
Related
I have an app that's close to launch. In prep for this, I've put it into production with "Timed publishing". It's ready to go, all I have to do now is click "Go Live".
However, I have a bug fix and I want to put out a beta for it now, before I'm ready to release the app to the world at large.
I've managed to upload the beta, but how can I release it to my beta testers through the store. Previously when I've played with Timed publishing, it didn't actually go out to the Beta testers until I clicked "Go Live".
I don't want to do that, because I'm not ready for my app to be made public at all, and I'm afraid it will go anyway.
I've tried switching to Advanced mode and Deactivating the version in production right now; however, it won't let me save. It complains The application could not be saved. Please check the form for errors. But don't see anything on the form that looks like an error.
How can I do this, or what should I be looking for to find the error?
I got an answer out of Google:
We don't currently support the functionality of removing production APK. If you press "Go live" button on the upper right corner, both production and beta version will be published on Play Store. It's not possible to keep production version silent and only have beta version live.
We currently require that once a Production APK has been published, the app must always have an APK in Production. This requirement is in place so that we are in compliance with the DDA by ensuring that once an app has been made publicly available, that it remains available for any users who may have installed it.
In my not so humble opinion, this is a deficiency in Google Play's system. I can see that requirement once it has been made public, perhaps even only after someone has actually downloaded it, but until then I as a developer should be able to pull it completely or be sure it's going to go straight to a Unpublished without ever appearing on the store so that no release happens by accident.
Google continues:
If you would like to prevent users from downloading your latest production version, since you haven't made it live, one option is to edit the previous production APK file to which you want to roll back with a higher version code than the current APK file. You may then upload the old APK as an update.
After you make sure the production APK is not the one you want to present to public and the beta APK is the right one, you can then press "Go live" so users will still see the previous production version while testers can download beta version.
The other way is to unpublish the current app and then publish a new app with a new package name for beta testing only. [...]
Both those are round about ways of accomplishing the work I need to do, it just adds more effort on my part to set up another app for my beta testers to use. It would; however, allow them to use both side by side on the same device when it goes live.
Right now I'm facing the same problem, but I think it's not possible to publish a beta if timed publishing is enabled without going live.
Here is the reference about this topic I found in Google support:
Reference link: https://support.google.com/googleplay/android-developer/answer/6334282?hl=en&ref_topic=7072031
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.
I posted an app into google play production section and now I want to download it for testing. It's not free. I don't want to buy it. How can I do that?
Uninstall your current app on your device
Go to play store and search your app
If you were an alpha or beta tester, renounce to it
Install your app again
I think the correct way is to have two applications, one for testing and one in release. It is really a mess because package name must be unique within the market...
But it is the only way I can imagine right now. Release one only for alpha/beta restricted users (you) and publish as paid one when done.
I´ve read also here How do I allow android app alpha/beta testers to download the app for free?
and here Google Play developer console: beta test paid apps for free?
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.
My application is currently in alpha. On the google play developer console, I accidentally uploaded a new APK as production rather than alpha.
In advanced mode, there is a deactivate button. But if I deactivate and try to save I get the generic message "The application could not be saved. Please check the form for errors." I don't see any errors on the form. How do I deactivate?
I tried uploading a later version to alpha - that seems to work - but I don't want ANY version in Prod, as my app is not yet ready for prime time.
According to a Google customer service rep I contacted:
The Deactivate button is provided in your advanced mode when you want to support multiple APKs but when your new update supports the same number of devices as your previous APKs, the system won't allow such update. So it is required for you to deactivate the older version in order to upload your new APK.
The Deactivate button is only useful for situations where you have multiple active APKs.
Furthermore, discussing with them, there is apparently no functionality at this time that allows for you to remove APKs from the Production tab once they've been uploaded to that tab, AND there's apparently no way to enable Beta testing if your app is unpublished, so at this point it seems there's no way to undo what you've done if you accidentally upload an APK to the Production tab by mistake. The workaround proposed by the representative was to change the package name of the app, change the keystore used to sign, and create an entirely new application.
Further discussion with the representative indicated that the "error" is that you can't have a Production tab without an APK if there was one there already, but it sounds like there's a bug in that it doesn't actually report that that's the cause.
In latest play console you can goto Publishing Overview->managed publishing status-> press manage button on right then turn on managed publishing