Usually the when the application gets released in the Internal Channel, the build will get reflected instantly. Within a minute.
But strangely the build is not reflected even after a day. I am using the latest new Google console which displays the status as, ('Release not live' and not 'Being Reviewed')
Can you help to understand the behavior or the cases which might cause this
This was happening to me when published an open beta version, it was the first release so in my case it was not a superseded version problem. I fixed it by completing the "Feedback URL or email address" field in the Open testing > Testers (Tab).
After doing that the status changed from "Release not live" to "Available to unlimited testers" with the green icon.
I've found it by pure luck since Play Console does not indicate where is the problem.
This usually happens when you have a production bundle/apk with a version code greater than the Internal Track's bundle/apk version code.
Check if that's the case.
I experienced the same thing. For me I had to complete the "Feedback URL or email address" field as stated above. Also in addition to that I had to go to App content and complete the Privacy Policy step. When I had declared that my app complied with Google Play Policies the status changed from "Release not live" to "Available to unlimited testers". Hope this helps someone.
I had another problem, so I summarize the both fixes.
1. Missing feedback url
Under Testing>Open testing>Testers fill the following
2. Bundle/apk version
Your bundle/apkversion code may be greater than the Internal Track's bundle/apk version code.
If it's your case, you'll have to publish a newer version.
3. Stuck on Publishing overview
If the publishing overview is set to Managed publishing on it wont be released neither.
Go under Publishing overview
Publish the content
If you do not have any version live now & this was the reason why you were using the Managed publishing
Change managed publishing to off (top right)
Go under >Setup>Advanced Settings
Select Unpublished
Warning: You can download an open testing version only if the app is published
Cheers
This can also be because you have previously paused the track.
The track needs to be resumed.
Hope this helps someone as I have stumbled upon this myself and spent some time until I noticed the track was paused (I forgot about it)
Related
Our app update has been rejected even though we addressed the issue. In the email with the details of the rejection says that we have some vulnerabilities with our recent submission but it says that the version that have issue is the one on the production channel:
and we didn't submit that version because it's already public, my latest version is 2021031602 (3.3.0) and as you can see in the image above that version doesn't have any vulnerability and I want to upload it to a closed test channel not production. I post this question here because I'm unable to get a proper response from the Google Play Team.
This is the most recent chat that I had with them:
Then I get this email:
But I never got an answer from the policy team, we have been running with this issue since January and honestly I don't know what else can we do.
Anyone who has been in this same situation? I'll really appreciate your input.
Greetings!
I managed to solve the issue with the following steps, in case someone is struggling to find how to remove a non complaining bundle/apk.
Go to your Play Console.
Select the app.
Go to App bundle explorer.
Select the non-compliant APK/app bundle's App version at the top right dropdown menu, and make a note of which releases they are under.
Go to the track with the policy issue. It will be one of these 4 pages: Internal / Closed / Open testing or Production. (If the bundle with the issue is on the production track, you'll need to upload an update directly to that track until you get to the step 8).
Near the top right of the page, click Create new release. (You may need to click Manage track first)
If the release with the violating APK is in a draft state, discard the release.
Add the policy compliant version of app bundles or APKs.
Make sure the non-compliant version of app bundles or APKs is under the Not included section of this release. For further guidance, please see the "Not included (app bundles and APKs)" section in this Play Console Help article.
To save any changes you make to your release, select Save.
When you've finished preparing your release, select Review release.
If the non-compliant APK is released to multiple tracks, repeat steps 5-9 in each track.
I've been developing my first app for work and am having trouble removing an earlier version from the Google Play Console.
My first release was version 2, which I released on the Internal Test track, as much as an experiment to understand the working of things. I have subsequently release the app up to version 8, always targeting Alpha/Closed Track and had no problems with them.
However my first release, the one in Internal test track, simply refuses to go away. All the others I have found I can click MANAGE then RELEASE TO BETA then DISCARD (at the bottom) and they go away, but not this one.
Can anyone help me with this please. I have to say that the websites for releasing to both Android and to Apple do leave much to be desired - a bit of a baptism of fire to get your first app out there, even just to testers.
It is possible to discard the release by creating a new release without a bundle or APK, inserting a release name, which is required, and completing the process.
We found that while there is no remove, we had to add an empty version which replaced the test version. This was a huge problem for us as the test version was in violation of permissions rules and our production code was not, but the production app was pulled from the Play store... Yikes. Adding a remove or delete would be soooo much more intuitive.
Sign in Play Console
Choose your app
Click Release Overview (Left pane)
Select the release version that you want to stop
View track
Pause track (Right upper hand corner)
I would upload your next alpha to the internal test track and promote it to the alpha/closed track. You will still have a build in the internal test track, but at least it is a relevant build.
Tried and worked.
Unfortunately, there is no straightforward way to delete or make a version inactive. The simplest thing you can do is as follows:
If not done already, create a version of your apk/aab you want to really release and upload it.
Go to test tracks where old versions are used. Create a new release in that test track.
Instead of uploading a new apk/aab, just pick the latest one from the 'Add from library' option.
Roll out the test track release.
It will simply mark old versions (which were used in test tracks) as inactive and only the latest one you uploaded will remain active. You can verify it on the 'App bundle explorer' page.
Now you can submit the app for approval.
End a test
To remove users from your app's test:
Sign in to your Play Console.
Select an app.
On the left menu, select Release management > App releases.
Next to the test that you want to end, select Manage.
Expand the "Manage testers" card.
After ending a test, testers won't receive updates but the app will remain installed on their device.
To remove a closed test track that you created, select Deactivate track. You can access deactivated tracks on the App releases page in the "Closed tracks" section.
To end an open, closed alpha, or internal test, select Remove testers.
Go to manage internal test
Manage testers
Remove all testers
This is the safest way
Haven't found how to delete a build - as been said, we just upload a newer version of the app with higher build number into the Internal track and propagate it through Alpha to Production. So just overwrite the unwanted build.
You can mark them inactive after pausing it.
I believe that what most are saying is that Google needs better way to disable or continue testing an obsolete or bad build when the developer knows it's a waste of time. It seems that there are ways we can force it, but it's not the ideal way. I agree. I don't want people to waste their time or bad-mouth my app because of unclear definitions on our side. We are in the 21st century, but everyone makes mistakes. If Google path is ideal, then make the documentation reflect that.
You don't need to discard it. Testers will always get the highest version code they are eligible for.
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.
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.