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)
Related
I had a build of my app in Google Play Open Beta. I released it to Production. Now, even though my friends are downloading it from the Google Play store, and they are not in my beta, it seems to be telling them that they can only use a test card for purchasing! How do I:
1) Close the beta completely.
2) Change it so people are spending real money in my app, when they download it from my app store?
It looks like people should be spending real money, from my beta page -- I've just removed all the testers and changed the country availability to just Aruba. My beta track page looks like this:
Have I made the right change? Am I just waiting for everything to propogate, now?
The actions I took after posting this question solved the problem. I needed to remove testers, and turn off the open beta test by restricting it to only one country, I guess. All done!
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 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've pushed a beta version of my app to the play store and am now trying to see it in the play store on my device. It's not showing up.
How can I tell whether it has been published?
When I go to the play store on my laptop and search for my app, only the production version shows. If I click on the search result, it goes to the app store page with a warning "you don't have any devices". That part is fine. But should the search results also show my beta version?
I've set up a google group of which I'm a member.
I'm assuming that if the play store shows it on my laptop and doesn't show it on my device, then I have some sort of configuration problem - that is what I'm trying to debug in the first place. However, without knowing if the beta version is published, I'm in the dark.
Any one know how to deal with this situation?
The best way to verify that the Beta app is installed on your device is to actually install the app on your device from the Google Play store using the account with which you have opted-in to the Beta Test group. You can then verify that the Version Code of the Apk is indeed the Version Code of the BETA Apk that you have uploaded. You might want to print the version code to logcat as your app stats so that you can verify it easily. You can then also opt-out of the BETA test and reinstall the app through the Play Store and verify that it is NOT the Beta Apk by once again looking for the version code.
The Play Store now allows open and closed beta testing, although this was not always the case. If your application is in open beta testing, then it should be in the search results, given you've got a version in production. (I'm lead to believe that if your app is in open beta but you don't have a production version, it will not be in the search results).
In order to test to see if your application is available in the search results, you must disassociate yourself with your developer Google account to do your search. This will remove the association that your Google account has already with the application. It sounds like you've done that "on your laptop" since it says you say it says you have no devices. If your computer is logged into Google, you'll need to open a private browsing window or log out of that Google account, then do your search. If the search returns no results, the application will not be discovered by new users. But those same new users could still be in the beta by using the beta link that you have the option of distributing.
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.