So google has changed their publishing interface so that Recent changes no longer goes under Store Listing but under a specific apk. The problem is, I don't see where to add those comments in the apk that is actually in production. For the unpublished APKs I can just go in "Show details". Does anyone know how to add those comments for the APK that is actually serving in production?
Go to https://play.google.com/apps/publish
Click on your application
Click on APK in the left menu
Click on the version you have in production
Scroll down to What's new in this version?
Click on the seemingly-uneditable text. It should become editable.
Save
Related
Is there a way to remove an update from the Google Developer Console?
Players that already have downloaded that update can keep it, but for those who haven't, I don't want them to download it as well.
My current "solution" to this is to just push an old version of the app signed with a new version number to the Developer Console, but I guess there's a better way, which I haven't figured out yet.
Thanks in advance.
In the Google Play Developer Console, select your application and select the "APK" menu option. This should display the current and previous versions of your APK. If you then click the "Switch to advanced mode" button, a "Move to Prod" button should appear next to previous APK versions. If able, these should allow you to move previous versions of your APK in production.
As title states. I clicked on "Publish" in the google play developer console. And it said my app now got uploaded. But I dont know which apk file was uploaded. How can I find out?
EDIT: I am 100% signed in correctly. Here is an image of the tabs on the left.
In the tab with the android robot picture, it says I have no applications. But in the tab with the google controller thing, I can click on my app, look at the game details, leaderboards, achievements etc and I can click publish but I dont know what it's publishing...
Go to your Developer Console (All Applications) and then click on the app. On the left, there is a list of things to choose (Statistics, etc.) so click on APK.
That will tell you everything about the version and version code of the APK. You can click on the latest version to get some details on it, and at the top of the page it even tells you the package name.
You can by checking the version of the app. Click on all apps -> apk, then you see a list of apk's you uploaded and the current version number.
Are you sure that your app is on play store and not only in play game?
If you upload it with your account should be appared in the tab with android's icon
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.
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.
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