My app is being tested using Google Play. I am one of my alpha testers, naturally. I released a new alpha version of the app. I was expecting it to update automatically on my device. But it's not updating. Am I missing a step? According to Google
Once they install the app and opt in, they'll automatically be updated
to the new test version.
Nothing with Google Play is automatic. They have a caching system much like Apple App Store among others. From my experience, once or twice a day the cache system gets flushed and the market gets updated.
At some point after that, the updates get pushed. This can be a multi-day process unfortunately.
Just had the same problem. My update wasn't available after 48 hours. Tried closing the app store and restarting the phone, which didn't work. Then I went into the phones settings and cleared the play stores cache, which worked immediately, and I could download the latest alpha version.
In addition to the time it takes for app updates to fully process, the Google Play app itself also caches app information, so your users (and you) may be seeing a cached version of your Google Play list.
Here's a trick to force Google Play to fetch the latest version of your app. This works every time for me.
How to reset the Google Play app's cache:
Force close the Google Play app
Open the Settings app
Go to Applications > Application Manager > Google Play Store > Storage
Click Clear Cache
The Google Play app's cache should now be reset. Try finding your app again and see if it shows the latest version.
Google announced on March 2018 the availability of an internal test track.
According to documentation:
You should create an internal test if you want to quickly distribute
your app for internal testing and quality assurance checks.
[…]
An internal test can have up to 100 testers per app.
I had a similar issue where my tester was able to see the production version of my app in Play Store but not the new Beta version update even though it was uploaded many hours before and available to other Beta testers as an update.
I had added him as a Beta tester to my Google Group, also added as a test user in my Google Play Store account. The solution was to force stop Play Store then restart it again.
The Beta Update was available as soon as he went back into the play store and searched for the app.
This might work for you:
On your Android phone or tablet, open your Settings (possibly represented by a cog icon), then click on Apps.
At the top of the screen, click the 3 dots in the top right corner to open more options and click show system apps.
Scroll down and tap Download Manager.
Tap Storage Clear Cache and clear data.
Open the Google Play Store and the updated version will be there to download.
reposting #Aeramor comment as an answer as this solved the issue for me.
Force quit AND clear the play store cache/data and it will update instantly
It may take some time to get the update from the android device. For me for "Internal testing", after uploading an update, I was getting it from my device for a while. Once I cleared the cache for "Google playstore" app of my android phone, I got the update immediately.
While clearing the Google Play cache resolved one issue for me, I noticed something else strange that may help someone out. When I clicked "About this app" on the app page in the Play Store, the version shown for my app was the previous version number. This made me think that the new version was still unavailable and I just needed to wait. However, after waiting several hours for the new version to appear on the Play Store, I decided to try downloading it anyway, and lo and behold, the latest version had been installed.
1 - Upload APK in alpha test
2 - Add your email in one google group or google plus community
3 - copy the link test provided by google play and press accept button
Now just wait until your application became updated.
It tooks 72h for me to update close testers app. Without removing caché or anything, just...waiting 3 long days :(
I found that the link I provided to testers was almost immediately going to the newest version. No need to clear cache or any other steps required.
Just check to see the link goes to the new version, then inform testers to click the app link for the update and install it.
fyi, this was for an internal test release with an email list of testers created in play console. Also, the first release had a delay before a link was available, but subsequent releases were available through the link provided to testers very shortly after rollout.
I did all of the above (cleared cache in Google Play and Download Manager), restarted my phone, and then checked for updates in the "My apps & games" located in the settings drop down (3 bars on the left of the search bar when opening Google Play) and there it was, voila.. waiting to be updated. About 5 minutes after I updated my app, I got my email saying my update was live.
Don't forget to pass in WIFI mode to get the update (depending of your settings).
Recently faced this issue and contacted Google Play Developer Support. Here are the instructions. Maybe it could help someone...
Please make sure that the tester email you used must not be opted into
multiple testing tracks. Please ensure that your testing group is only
enabled in only one testing track.
I recommend you to opt out of all the testing tracks and clear the
cache and data for the Play Store app and your device’s download
manager. This will clear any settings and temporary information saved
to your device. You can still access purchases you’ve made from Google
Play, like apps, music, movies, and books. Here's how:
Open your device's main Settings app.
Tap Apps or Application manager (depending on your device, this may be different).
Tap Google Play Store
Tap Storage.
Tap CLEAR CACHE > OK.
Tap CLEAR DATA > OK.
Tap the back arrow to go back to the main menu.
Select Downloads or Download Manager.
Tap CLEAR CACHE > OK.
Tap CLEAR DATA > OK.
Relaunch the app.
IMHO, the most crucial point here is the following:
Please make sure that the tester email you used must not be opted into multiple testing tracks. Please ensure that your testing group is only enabled in only one testing track.
Accessing Google Play test app updates
TLDR:
add users to tester list with email matching their device account; internal testing track is fastest; they must opt in using app-specific link on the web; if testers don't see update, have users Force Stop and clear app storage for Google Play Store, then visit your app's listing page in Google Play Store again.
Notes on getting/giving access to beta test updates from Google Play
Internal Testing is the fastest. Other testing tracks can take time to Review and release. You will get an email when the review process is complete.
Testers will need to opt in from an app-specific link; this is emailed out to each user the first time they're eligible to test a release, but it's also available from Play Console (see screenshot below)
Testers must be signed in to their Android device with an email/account matching an entry in your Testers list (e.g. Internal Testers)
Once the Internal Test is released, or the Review process is complete for Closed/Open testing, apps can be updated from the Google Play Store
Google Play Store caches app data, so it may take time for any particular device to show available updates. To see available updates immediately: Long press on Google Play Store, visit App Info screen, Force Stop, visit App Storage screen and clear storage, reopen Google Play Store, and visit app page; you should see any available updates.
Edit testers from Play Console > select app > menu item Testing > [Internal|Closed|Open] Testing
Example instructions for testers:
Visit this link and click the button to opt-in to testing (Example link: https://play.google.com/apps/internaltest/INTERNAL_ID/join?hl=en-US)
Open Google Play Store and search for App Name. Open the app listing.
If you don’t see an option to “update” the app, install a test/beta please Force Quit and Clear Storage for Google Play Store:
Tap and hold on Google Play Store app icon (you may have to swipe up to find it, or it may be in your “recent” bar at the bottom of the screen)
Tap “App info”
Tap “Force Top” option on App Info screen
Tap “Storage & cache”
Tap “Clear storage” option
Now visiting Google Play Store again and search for APP NAME
Install/update the beta and open the app again
Related
I had an app that was in the Internal Testing phase, and I had added my own email to the internal testing list of testers. Now, I want to download the release on the Open Testing track, but when I visit my app listing on the play store, it still shows "(Early Access)" behind my app name.
I tried to follow the documentation for leaving a beta program, but there was no "Manage apps & devices" button when I clicked on the profile icon on the play store on my web browser.
So then I started up my AVD, opened up the Play Store and signed into my account, then I managed to find my app in "Manage apps & devices", but there was nothing there about leaving the beta program.
I also tried to remove the email list containing my email from the Internal Testing track, and then also paused the Internal Testing track, but I still see "(Early Access)" in the Play Store.
Then after more searching, I found this thread . I followed it and tried to add "/leave" at the end of my internal testing app URL, which worked (which already doesn't make sense since I already removed myself via the Google Play Console), but after clicking the leave button, I STILL SEE "(Early Access)" in the Play Store!
Must I create brand a new Google Account just to see the Open Testing of my own app??
(Edit: to clarify, I have not released my app to production yet. However, when I view the app on play store without logging in to a google account, I can see the Open Testing version, without "(Early Access)" behind the app name.)
I have an app published to Google Play Console for Internal Testing i.e. I just want this app to be available to certain users. Below is the current summary of the app;
Note this is the second release i 'tried' to see if there will be any difference; I first uploaded a .AAB file then in the latest release I uploaded the .APK file.
Below is the link I send to my testers;
Issue is that when a tester clicks on the link, they opt in the 'programme' and have an option to download it on google play. When they click on that link, its either just infinite loading or a message to say the requested URL was not found on this server.
Please note this app has not been published to the play store as a
live version.
This is the first time the app has been uploaded to internal testing.
The app has been first published for internal testing last Friday (6th of Nov) and now is 9th of Nov.
On the dashboard, there is an announcement as shown below but I cannot see anywhere the 'status' of the app i.e. to say its being reviewed etc.
Reply from Google;
I understand you have some concerns about app pending issue. Please note that after you submit a new app or an update to an existing app on your Play Console, it can take some time for your app to be processed for publishing on Google Play. Any time you make a change to your app while a review is already pending will mean the review period starts over. Furthermore, any submissions can't be retrieved or cancelled. As a result, we recommend you adjust your planning to account for this and avoid resubmitting.
For certain developer accounts, we’ll take more time to thoroughly review your app(s) to help better protect users. This may result in review times of up to 7 days or longer in exceptional cases. You can always view the current status on your Publishing overview page. When the review is completed, you will see "You don't have any changes in review" under Changes in review section. In addition, we would also like to remind you that if you turned on the managed publishing mode, your update won't be published until you click "Review and publish."
Facing the same issue. Uploaded a new app on Nov 6th. Still waiting for the app to be available on the play store for internal tests. Followed the procedure to enable internal app sharing from the play store app which is:
Go to settings on the play store app
Tap on play store version seven times to enable internal app sharing
Enable internal app sharing.
Even after following this procedure, the app is still inaccessible to my internal testers. From research, I've concluded it might be due to the IARC content rating not having been accepted yet https://stackoverflow.com/a/63651644.
UPDATE: I was able to get my app available to testers later on by going to Publish Overview and clicking on 'Review and publish' button.
Had the same problem. Now my app is visible to internal testers.
You have to finish all the checks and formalities before your app shows up on the Play Store like agreeing to the tncs and privacy policy, adding descriptions, screenshots, etc. I also enabled sharing of app via URL by going to Setup > Internal app sharing
We recently released an app on google play and after a couple of beta versions I moved it from beta to production. However, some people cannot download the app. Here is an example from Vietnam:
I don't know Vietnamese, but I asked a colleague to translate it and it says:
"Another account, {{email}}, has joined the beta program of this app. The updates for this app could include many beta versions."
Does anybody know how to solve this?
Google Play Store seems to store the application and user account association information in the device's local storage. Clearing the data of the Google Play Store from its app info page should do the trick. Now simply switch the the account that you have joined the beta program with and you should be able to install / update the restricted app version.
If it still doesn't work, repeat the process but this time reboot the device.
Another option is to install the app remotely through google play's website. First remove the app from the device, visit the site with the required google account and install the app in the device of your choice remotely.
This should not block updates, it should only be a warning. The English version of the message is "Another account on this device, XXXX, joined this app’s beta program. Updates to this app might include beta versions."
(Good translation by your colleague).
This is a device with more than one gmail account associated with Google Play. It is probably either shared by multiple people or the user has multiple gmail addresses.
An android device can only ever have one version of an APK (with the same package name) on it installed at once, even with multiple users.
The warning is saying that the current account looking for an update is not enrolled in the beta program for the app. However, another account on the device is enrolled in the beta program. This means if this user does an update, they might get a beta version of the app (as the upgrade as to be appropriate for the other user too). The warning is displayed so the user doesn't unexpectedly get a beta version.
However, it should only be a warning, it shouldn't stop the user updating.
There's a way to bypass this guys, should you want to install the application. On the app list when you search for the desired application, click on the "..." symbol at the upper right corner of the application, there is an "Install" option for you.
There is a button on left top corner, for google play store options. There, change the user to a the one they say that can use the program (different e-mail adress), and you will be able to download the required app.
I have published an app in Google Play a few months ago. That app have some downloads and data from users in Console Google. I will release a new version, but while I'm finishing, I want remove it temporarily - keeping all that data and download numbers. Is it possible or when I cancel the publish all data will be deleted?
Please note that you unpublish (and this means just what name says, nothing more) not just APK - you hide all related stuff (app's page in Google Play etc). To end user it looks like the app is gone. For you - it is still in your console, you can edit description, images, see comments, stats or update APKs etc., but unless you publish it again, nobody will see these changes.
https://stackoverflow.com/a/13493065/7303462
You could do that by unpublishing your app. You can re-publish it by installing a newer apk of the app and all the data will remain the same, you'd not loose any of it.
PS: You cannot delete an app from your account. Published and unpublished apps will remain in your account.
Update 2022 :
You can go to "Google play console -> Release -> Setup -> Advanced Settings", but as google says :
Unpublished: New users cannot find and install your app. Existing users can still find it and will receive updates.
Published: New users can find and install your app
I found a solution so that you can restrict the region of your app if you do not want to delete and republish it. This prevents even existing users from finding your app. In the published list of your app, you should keep at least one country, and you can select the country with the lowest downloads.
I think I followed all steps which I have found so far but the download link for my alpha test isn't working.
I uploaded the app 3 days ago, created a google group and added the group to the list of alpha testers.
I invited a few members and the app status shows published, after clicking on the link I can signup as alpha tester, but when I click on "Download from the Play Store" the error message "We're sorry, the requested URL was not found on this server" comes.
Did I miss an additional step? Do I have to grant some special rights to the group members somehow?
--- update can this be caused by the permissions of the app?
under the apk info in the developer console I can see:
functions:
android.hardware.LOCATION
android.hardware.location.GPS
android.hardware.location.NETWORK
android.hardware.TOUCHSCREEN
permissions:
android.permission.ACCESS_COARSE_LOCATION
android.permission.ACCESS_FINE_LOCATION
android.permission.INTERNET
-----UPDATE2
Well I don't have any idea what changed but now the download link is working for my alpha testers.
For me, it resulted to be a cache problem so deleting the cache in Setting > Apps > Google Play Services > Storage > Clean Cache and deleting chrome's cache, did the trick.
If your app is published in alpha or beta version :
it won't be shown in search results,
use the link that google play sent you in the group of testers in order to open it in Google Play application.
(see edit below)
You can also open this URL : https://play.google.com/apps/testing/APP_PACKAGE with a browser if the email configured in your phone is a member of the google testers group.
i don't think permissions in manifest can hide an app of the store !
EDIT
After you have uploaded your APK file and published it to Alpha or Beta version, you will see a link "manage testers group" or something like that. Click on that link ... you will be asked to add a google group of testers, below the popup you will see a message like this : "share this link with you testers group". Copy that link and send it to the group by mail.
Sorry I am writing with SO android app, I can't paste screenshots therefore ... may be tomorow ;-)
Hope it's ok.
I don't have any idea what changed but now the download link is working
You issue was just the publish delay -- it takes some time for Google Play servers to pick up your submission (for any publishing operation, even with alpha builds), usually under 24 hours.
Try opening the link on both your test device and in a desktop browser.
I was able to sign up as a tester from the device, but not install the app (said not found), but going to the desktop browser was able to use google pay to install it remotely to the device.
Make sure its the url in the form https://play.google.com/apps/testing/{your.namespace}
Sign in to your Goole Play Console.
Select your app.
On the left menu, Select Release management -> App releases.
Select Manage Alpha or Manage Beta.
Manage testers, click on right side down arrow.(Just below CREATE RELEASE)
Choose a testing method: select Closed Beta Testing.
Next Create list or select the name of your list.
Feedback Channel: Enter your email to get feedback from testers.
Copy Opt-in URL and send it to your testers.
Now once you completed, Google Play servers takes time for any publishing builds alpha or beta. For me it takes 15-20 minutes to available.
Sometime clear cache of your browser and refresh link. will work.
Once link is available, Open it in your testing device and click on below link
Download the *APP NAME* app on Google Play
Press the Update Button. After installation you can test it.
How authorized testers turn on internal app sharing
Before authorized testers can download apps using internal app sharing, 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. Tap Turn on.
I'm having the same problem, the link simply doesn't work, 36 hours after publishing. Might as well not even provide the alpha/beta features if it's going to be like this.
Anyway, I'm sharing some information provided to me by Google Support, hoping it'll be helpful:
Ensure that you have added a valid Google Group email or Google+ Community URL to the Developer Console and that you are included in the group/community. Once the group/community has been added, the name of the group will display in the “Manage list of testers” link in the testing tab. (Please note when adding a Google Group you need to enter the email address and not the URL).
If you wish to use a Google Group in a Google Apps domain, the Developer Console and Private Channel must be enabled for your domain in the Google Apps Control Panel.
An app must be published for several hours before the opt-in link will become available to testers.
Currently, testers must have only one account on their device. Devices with more than one account will receive the production version of your app. (Please note this requirement is temporary. Stay tuned for updates).
If you followed the mentioned instructions and it's still not working, in 2019 make sure to also check the following:
1) Make sure the testing group is selected, but is also active:
2) Ask your testers to log out of their google account, then to clear the cache of their browser. They should then close/re-open the browser and log in into the invited email address.
There are several causes for the internal/alpha testing link not working:
1-You are on a different google play account
2-Your email is not added at the email list for testers
3-Go to google play console> your app > app releases > internal test > make sure list name is check as if not the testers will not have access to the app
Hope this helps to solve the issue
One of the causes of that issue might be its availability in (one) particular country only. (USA, usually).
In that case you just should go to the app details and allow its distribution to other (local) stores.
My problem was that even though I deinstalled my release version the link from internal testing brought me again to the release version. This fixed it.
I had this problem if I was logged in with multiple different Google accounts. I opened a new private browsing window and logged in with the account that I wanted to use as an alpha tester, and then the download link worked.
I got the same issue, seems a bug. Solved by:
1.Click "unpublish".
2.Wait for a while, click "re-publish".
Then my App became available in a few minutes.
In my case I was listed as tester in several list (alpha and internal test).
I had only joined the alpha testing channel and I had no way to access the app via the link nor via searching the store.
And as soon as I also joined the internal test channel.
The link to the app magically started working.
So I guess the rule is: you need to make sure you have joined the most privileged testing group that you're invited to.
Also make sure the app, you're going to test, is uninstalled from your device.