yesterday we are created a new app in Google Play Console. Then we upload a new release APK into Alpha-Track, added emails for test-group and waiting already more then 24h. Nothing happen. We can't see any opt-in link for testing...
Today early morning I created a new "internal"-track for testing (in google docs stay that the APK-file will be available for testing after 10-15 minutest after publishing)...
We waiting already many hours and nothing happen...
What we did wrong or maybe something missed in configuration to start testing before publishing app in real store?
The first upload of an APK or App Bundle to the Play Console may take a bit longer to go through validation. It's not uncommon to have to wait 48 hours or more.
The internal app sharing indeed advertises the app being available within minutes, but that's only after having successfully passed the first validation. Once your app is available in one track, then every future uploads to internal app sharing should effectively be available within seconds or minutes.
In the "Manage Testers" section of the "Internal test" track, there should be an "Opt-in URL", see screenshot below (this is just a portion of the URL, usually a number appended to the end):
You will need to send this URL to any of the email addresses of testers you'd like to test the app, for them to be able to see the app updates from the Internal Test track.
I'm trying to publish a PWA on the Google Play store, and coming up against some confusing problems testing as an internal app. I used PWA2APK to convert my PWA to an APK. There are not major issues found through the pre-launch report, and only one accessibility warning. The project passed all of the requirements for the Play Store in December. I am the only user on the internal app testing list, and I receive an error message when attempting to install on Android through the internal app testing link. When I hover over the info symbol beside the project, I get this pop up:
Only testers can view this listing on Google Play because you haven't
uploaded any APKs to Production yet.
However, I posted an APK to Internal Tests on December 17, 2019.
When I click the View on Google Play link I'm taken to a URL not found page with the text:
We're sorry, the requested URL was not found on this server.
When I use the internal testing link to download the app on the play store on my mobile, I get a page with the app logo, title, and developer name, as well as the price on the download button. When I click the button I get an error message:
Error
The item that you were attempting to purchase could not be found.
I have checked out the advice on this thread, but am still having problems. Any advice is appreciated!
For anyone still running into this, make sure to go to Settings -> Internal App Sharing and accept the terms. The Play Store link started working instantly after doing so.
May be your IARC Content Ratings has not been accepted yet. Just wait for one or two more days. It will be accepted and app will be available on play store. If it doesn't create a new IARC Ratings.
As #ShabbirAhmed mentioned, it likely just requires waiting for the IARC Content Ratings to be accepted. However, in my experience you will also need to access the link through the most recent dashboard system, and not through links provided prior to April 2020 (at least). I will update if any new info comes up from Google Play.
I have seen 404 when I am not logged into Google services on the phone using the same email address as entered for me in the list of internal testers.
I see the something similar when I go to the link using a desktop browser. If I am signed into Google services I get a message saying to open the link on an Android device. But if I click the link when not signed in, I get a 404.
I think this is a form of security to stop the link from being shared with people that are not testers.
Problem Statement
I have setup my already published app for an internal test track according to the instructions provided by Google. However, I do get redirected to the page as shown in the image below. When I click on download it on Google Play, I am always redirected to the public version of my app instead of the internal testing version.
Background
I have introduced a functionality in the app that redirects the user to update the app. Prior to releasing to production, I would like to test this functionality with a group of internal testers.
What I've already tried
I have setup the testing users correctly by creating a list of such users.
I have referred to this question and have completed all the steps of publishing and shared the opt-in URL with my testers.
I have also referred to this question and have waited for multiple hours, as well as cleared Play Services/Browser cache on the devices that have the invited testing account set as the primary account
What I really want
What I would like to happen is to gain access to the Play Store listing page of the internal testing app and redirect to it from another build so that it can be ensured that after the update, the app works as required.
I'm not sure exactly what you mean. The listing for your internal version of your app is exactly the same as the listing for your public version. The user gets a small notification "you are a Beta user", but that's the only difference.
What do you expect different in the Internal listing?
My internal test version became visible on Play Store after 72 hours, which seems to be far too long for an app that has been in the market since the last 1.5 years. The answer provided by Nick Fortescue is correct in essence since I was expecting a different channel where I could access the internal test build.
I am working to publish a private, internal release for our app in the Google Play Store. I'm getting a message saying "An opt-in link will be available here when you publish your app", but I don't know what else I need to do publish my alpha test apk.
The release status says "full rollout", which indicates to me that everything is done.
I know it takes hours for it to appear but I already waited for days. What do I need to do to get this URL? If I sideload the apk that I created, will it be the same as downloading from the store (in terms of IAP authorisation)?
It's just a matter of time
Rolling out merely gets you to the Pending publication stage
After some time (say 45 minutes) you will reach the Published stage and the Opt-in URL
For many developers, it's just a matter of time. Rolling out merely gets you to the Pending publication stage. After some time you reach the Published stage and the URL will appear.
However, for your app, it looks like this app in unpublished. You can't opt-in to unpublished apps, so the opt-in link isn't shown.
For questions like this the Developer support team are usually really good, and we do have bugs sometimes, so it is always worth asking them.
When you create an internal test, you release your app immediately to your internal testers. This can help you identify issues and receive feedback earlier in your development process. An internal test is:
Fast: You can distribute apps via the internal test track much faster than the open or closed tracks. When you publish a new APK or app bundle to the internal test track, it will be available to testers within a few minutes.
Note: If you're publishing an app for the first time, it may take up to 48 hours for your app's internal test to be available.
Flexible: An internal test can be adjusted to support different testing stages, including internal testing, quality assurance checks, and post-launch debugging.
Safe: With the internal test track, your test app is distributed to users via the Play Store.
Be sure to check that you've completed all the required steps for publication! On the left sidebar of the Play Store for your app, check that there are no "!" icons; everything should have a green check-mark.
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