Hi i have uploaded my app to play store but till now it's in Ready to Publish state. Why is it i am unable to understand this? I uploaded my app on sep 13, 2013.In the attached pic on left side you can apk, store listing and Pricing & Distribution are ticked Green. If i hadn't fulfilled any part then it won't be Green
As you can see it on screenshot. Any idea why is it?
Try it in firefox. The drop down didn't open for me in google chrome.
If you are not the owner and have been added to a publish account this inability to publish can be also down to the permissions you have been granted. I had this with a client and they had not granted me access to manage production or manage alpha/beta apks. Once they granted this to me I had to log out and back in for the changes to take effect.
If Publish button does not appear in IE, try Chrome.
You need to Publish the app manually by clicking Publish option from "Ready to Publish" dropdown.
For me, the "Ready to Publish" button wasn't doing anything. I assume this is the problem you're having.
I opened an incognito window and signed in as a different user (owner rather than admin) and it worked fine. So, one of those two things solved it, but I'm not sure which. Go ahead and try either or both.
FWIW, this was in Chromium 35.0.1916.114.
Thanks to all the people who have answered for the question. It helped me lot. You need to publish the app manually by yourself. I am just trying to combine all those answers in one:
You must have admin privilege to publish the app so make sure you have one to publish app.
Try it in different browser. (In fact I didn't had to change the browser.)
Kudos to people who answered it.
You need to store listing , click on review then rollout
In the new Play Console, go to Publishing overview. Click the blue Review and publish button.
Related
I've successfully completed the publishing process for an APK to the Internal Test Track.
But when I try to view the App for download on the Google Play Store using the "VIEW ON GOOGLE PLAY" link in the screenshot below...
...it opens a new window with the following error:
I've also tried using the testers link "download it on Google Play." below...
...but it results in the same message stating the App can't be found.
This is the first time the App has been published and it's being done on the Internal Test Track.
The automated testing picked up a few warning and minor issues but no errors:
Has anyone experienced this issue before? I've contacted Google support for advice but I thought it would be worth trying here too and seeing if anyone had any suggestions on what to try next.
Thanks.
If this is the first time your app is being published on a track, it will take a couple of hours to be processed. This is only a one-time thing though, for future updates, the availability will be immediate on the internal test track.
Once the app is available, you'll also need to follow the opt-in link to be eligible for the download of the app.
Please delete cache and data of google play app on your device, then new updated version will be available
For Android App Bundles (AAB)
On the left menu, select Release > Devices and versions > App bundle
explorer.
Select the artifact filter near the top right of the page.
On the “Choose an artifact” table, select the right arrow on the
artifact you want to view.
Select the Downloads tab.
To share a link to install a specific APK: In the “Internal app
sharing link” section, select Copy shareable link.
As of today, the format of the shareable link:
https://play.google.com/apps/test/<package.name>/<version.number>
For Both APKs and AABs
You can use Internal app sharing instead.
Upload an APK or app bundle on the internal app sharing upload page
Then you can make your app available to anyone by sharing a download link.
Before anyone can download, they need to turn on internal app sharing on their Google Play Store app.
Open the Google Play Store app Google Play.
Tap Menu Menu > Settings.
In the “About” section, tap the Play Store version 7 times.
After the Internal app sharing setting appears, tap the switch to turn on
internal app sharing.
More information can be found here.
Answer for latest play console 2021
I was having same problem but since play console is lot different I didnt found any suitable solution but after trying a bit, this was solution that worked for me.
Play Console > Setup > Internal App Sharing > Email Lists > Make sure your email list is checked and saved.
In uploader and tester section make sure 'Anyone you shared link with can download' is selected.
Thats it.
I also created video on how this problem can be solved:
https://www.youtube.com/watch?v=gAiu76l4-7s
I just went through this completely unintuitive process, so let me clear up some myths:
Internal testing does NOT require the app be publicly released
The review process for your app apparently needs to complete before the app is available, as others pointed out, but the Play Console gives no indication this is a prerequisite, and happily states in several places that the App is available to internal testers when it is not. In my case the review took about a month to complete, which is why the "We are experiencing longer than normal review times" message was appearing in the console. This was the initial creation of my app, so I don't know which items-under-review were actually required, as the whole backlog completed at the same time (also with no notice to me).
Even at this point, if I follow the 'join' link on my phone, I still have the same issues the OP had. Clearing Play Store cache and other tricks did nothing. Instead, I had to click it from a PC, follow the prompts, and choose to install to a specific device (which requires the 7-tap developer mode on the device mentioned by others)
My case, hope it help. (Internal testing)
Make sure:
Change your version code for new release.
Add tester emails.
After upload and share link, must do these steps to download:
Open the Google Play Store app Google Play.
Click the Menu icon Menu > Settings.
In the "About" section, tap the Play Store version 7 times.
Once the Internal App Sharing setting appears, tap the switch to enable internal app sharing.
Click Enable.
Hours on this.
In my case the missing step was to enable Managed Google Play, which "Manage your private app and make it available to specific organisations". You don't need to apply an organisation filter, and simply use the internal test tracks.
The setting is found in Setup > Advanced Settings > Managed Google Play
#pierre was right. But that was some time ago, and now that link is not called Opt-in URL, but Join on the web. Just ask your testers to open it before they download the application.
We just had a related issue in this completely horrible process - documenting here because it burned a week for us.
Problem: We got approved on closed and production 2x but no one could see our app in internal, closed, public test tracks or on the public store.
How it happens: As far as I can tell when you start a Closed Test Track an organization gets auto-selected on Setup > Advanced Settings > Managed By Google and/or you can (irreparably!) set one yourself on the Closed Testing page. This means that only people in your org will be able to access it.
Solution: If Internal/Closed/Production is not showing up the solution may be: In Setup > Advanced Settings > Managed By Google you UN-check your org for it to be publicly available, as in the helpful alert in the screenshot below.
Duh. Worst default ever? :)
For me, i clicked the link play console gave me on phone
https://play.google.com/apps/internaltest/***********
But it didn't work, i clicked the link with pc, got the play store link, and clicked link on phone, and it worked !
For me, the issue was that of the version X.Y.Z, Google Play Console uses Z to determine the newest version of the app. So if, for example, the previous version of your app was 1.70.170, then 2.1.171 would work, but 2.1.1 would not show up for you as it would be considered older than 1.70.170.
Once you got the application from google play store link will be available on internal testing page inside.
Click on Internal testing
Step 1: Click copy link and use any browser
Step 2: after that it will show Accept Invitation already you are opened your added mail id from the google play developer console for internal tester on this application.
Step 3:
finally click on download it on google play
thats all. enjoy your coding...
Go to settings --> then internal app testing and add your testers there. Follow the instructions in this video https://www.youtube.com/watch?v=gAiu76l4-7s
I was running an app in the Google Play in Beta and then just recently "released to production" using a higher version APK.
However when I go to Google Play listing my app still says AppName (Beta)? I thought it just needed some time to propagate but I made the change 2 days ago and its still showing like that.
Anyone know how to correct this?
It actually looks like its some kind of caching issue or user specific issue.
I decided to open Google Play store from a different browser (where I was not logged in) and the app was no longer showing as Beta.
Only when viewing Play store from my logged in account and from my phone is it showing (BETA).
So for any non-beta testers viewing it for the first time on their phone or via browser I assume its going to show up correctly, which is good enough for me.
It seems that this is from the user's account side. If one specific account subscribed to a beta program it will show as (BETA) on the Google Play Store.
So to remove the beta the user just has to do the following:
Open the Google Play Store on the device.
Find the app he wants to leave.
Tap the app to open the detail page for the app.
Scroll down to find the section on beta testing.
Tap Leave.
Note: I Didn't find out a way to remove this on the Play Console but google i think they should have an option to do it.
I face the same issues . I have published my app two days before but it still showing that App Name(Beta). This happens due to only if you are the beta tester of that app .When you see it from another browser or other google play store ,It won't show beta.But keep in mind that you aren't a member of tester for this app.
To resolve this problem do these things:-
Please remove your account as beta tester from that app.
Or, Log out from device.Again login google account in your device .
3) Clear cache of Google Play Store.
Perhaps ,this will help you. Thanks..
It is due to Play Store caching , clear data of the Play Store , you will no longer see it as beta, plus make sure you are trying to see app on play store from a non-beta account.
It's simple l, just delete the tester list from testers in internal testing console, then clear cache from playstore, your good to go.
I had this problem and it turned out to simply be that I was logged in to google with an account that had signed up as a beta tester. I logged out of google and then the page displayed correctly. So it seems to me the (beta) is related to your account and not the software release which is sub-optimal coding on the part of google.
It showing AppName(Beta) just because of you are a Beta tester for that app.
There are two options:
Logout from browser and then check(different user that should not be a tester)
copy URL and open in in different browser
In my case I had to clear storage of play store application on my device.
Somehow I could not update, my test track was paused, there was no way to opt out so out of desperate I just cleared storage of play store app and done, everything back in normal. PS: Yeah I also deleted app and reinstalled before that maybe this was not necessary, don't know.
Although #Ruben Miquelino's answer is correct, it is not practical to ask every user (users already on beta) to go to a link and remove beta.
I have found a better solution for this problem, If we deactivate the beta track and change target countries(only for beta) then those users will automatically be moved to Production (after Google's review process & Play store cache expiry)
I couldn't understand why the 'Unpublish app' button in Google's Developer Console isn't available (I can see it, but not press it).
It looks as if the link is disabled.
<a class="gwt-Anchor gux-disabled" disabled="">Unpublish app</a>
Anyone has any idea why is it so?
You have turned on manage publishing that’s why your button is not working
You have to turn the manage publish off. Then this button will work.
For more you can see this solution video
https://youtu.be/EaH1Ls04uK8
If the Unpublished button is not working - you have to turn off
the Managed publishing status. See these attached screenshots:
On Google Play Console:
Open Publishing Overview tab. If Managed Publishing turned on, then turn it off by clicking the 'Manage' button.
Now you can open Advanced Settings and unpublish the app by choosing the 'Unpublished' switch. Don't forget to Save changes.
That's it ))
This is most probably because the app is still being distributed. It takes a couple of hours for the app to the released. This depends on the localisation of the app. if you left this default, the app will be distributed worldwide.
According to Android Authority:
It takes a few hours for the app to appear. The publication process
is automatic and it isn’t too long before your app becomes available
for download.
Wait for a bit and try again. It also seems very wierd from Google, however the label has a grey color, making it seem unavailable. In fact it would be available, when clicking on it.
From my understanding, you cant un-publish an app that is being used. Or after more than 24 hours of publishing.
This is to stop you un-publishing an app that someone has purchased etc.
I had to contact their support team to remove one of my apps. And they something similar to the above (which criteria i met as only I had installed it), so were able to remove it for me.
Contact support for more help / advice on the issue, specific to the app you wish to remove.
I uploaded my beta version of the app and I want to deactivate the production version. I figured out how to click switch to advanced and deactivate the production app but it will not let me save it, always give me in red at the top " The application could not be saved. Please check the form for errors." but I see no errors show on the form.
Any suggestions on how to get past this?
Here is a screen shot:
This has happened to me quite recently. I tried to unpublish an app and got same error. I found that the questionnaire for content rating was incomplete. I updated that, applied the suggested content rating, and voila...I could unpublish the app without any error. Try to see if anything in your app settings need update, fix them and see if you still get the error.
More then likely you have not visited the developer console in a while. Lots of new things have changed with android in the last couple of years. You will need to fill out the new required information.
This includes things like rating, and new images that are required.
If you just want a tool to generate assets and than unpublish the application checkout norio.be it's a graphics generator.
The application could not be saved. Please check the form for errors.
Its happen when you can't complete the store listing
go to store presence >content rating > fill the form > apply> then you can finally unpublish it with out any errors
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.