I'm trying to test the in-app purchase of a consumable item on Android, but I'm unable to do so, as the item appears as being unavailable in my country:
This only happens when I'm testing on a device connected to Android Studio (which I need to be able to do) - if I instead download the app onto the device, the consumable item appears normally, i.e. as being available.
Some details:
I'm testing on a physical device running Android version 6.0.1
That device is running the latest version of the Google Play application
I'm testing with a user that has been set up both as a track tester and a license tester, and that is also currently signed in on the device
I've made the app available in all available 177 countries and regions
The app does not have a production release, it's only available on the closed testing track
If you have uploaded the build from the closed track, please ensure that you have accepted the test invitation from the invited email or it will show this error.
Step 1: Go to Release -> Testing -> Closed Testing
Step 2: Click on Manage Track
Step 3: Click on Testers tab
Step 4: Scroll to the bottom and you will see 2 options. Copy the link for web and open the link in your phone or browser with the test email you want to test.
Step 5: When you open the link you will have an option to Become A Tester. Click on that and then you are good to go.
The solution in my case was to select the app in the Google Play Console, then go to Release > Production > Countries/regions, and add the countries/regions there. Having the countries/regions selected in the closed/internal track only is not sufficient. It seems this is necessary regardless of whether one actually has a production release or not - again, in my case, I did not. It took maybe 10-20 mins after I made the update until I stopped seeing the issue.
TL;DR:
Upload to the Internal Test track and make sure it has the highest version code
I was having this issue for a few days, and also tried numerous things, but to no avail.. I uploaded my app bundle to a Closed Testing track in the Play Store, which did not solve the problem. After countless other methods, I eventually tried to upload a bundle to the Internal Testing track, which immediately solved the issue and allowed me to use test cards again.
Related
I have found the other versions of my question on SO and have already tried to contact Google through their dev support trying both the chat/email options, but have yet to get a straight answer about this.
I have an app that is currently using the internal testing track on Google Play. I have numerous testers all of which can download the app, use it and test it no problem. The reason I want to use internal testing, for now, is that the documentation states there is no verification period between versions and testers get the new version immediately.
The issue I am currently experiencing is that a tester who already has the app is not served an updated version when they return to the store page. If they uninstall and reinstall the app, the new app they install serves the new version.
My question is why would the new version be available but not present the user with the 'Update' button to install the new version?
Is there an issue with the app being on the internal test track? Does my app need to be verified? Can an app be verified using the internal test track? It has been 17 days since my initial upload to verify the app, which seems rather long to wait for the verification.
Does anyone have some insight into this issue? I am running out of ideas and it is rather annoying to have testers need to uninstall and reinstall the app every new version I would like tested.
After almost a month I finally have the update button. Here are the steps I took:
Create a new Closed Testing Track and go through all steps required to post a closed testing app.
Wait until the app is verified and the store page updates with the relevant store page data. (This took ~3-4 business days)
I can now publish to the Internal Testing Track, see the Update button, and use it. I no longer need to publish to the Closed Track unless I want to.
I've looked over most of the documentation and nowhere does it say in writing that your build needs to be verified to have the Update button appear, nor does it say anywhere that it is required to be in at least Closed Testing to be verified.
I hope this helps someone else in the near future as this was quite annoying.
Although a little cumbersome, when using internal testing, you'll provide your users with a URL where they can download the app (via the play store), note, this URL can be found under your "How testers join your test" section, on your "testers" tab, on your 'Internal testing' page.
When you create a new version, the testers who already have the app installed, can use the same URL provided in the first place, and they can click to download via the play store (counter-intuitive as they already have it), but when it takes them to the play store, it will give them an option to update the app, and you'll see your updated release note ect...
This means you won't need to go through the Closed testing approach and wait to get it verified.
I hope this helps somebody, I didn't want to create a closed tracked and get it verified as my app is very early into dev.
I have an Android app that is currently on an Internal Test Track (Version 1). I am trying to upload a new version (Version 2), but I want my current users to still test Version 1.
The console will not let me retain Version 1.
Is there a way I can have user Group A test Version 1 and user Group B test Version 2?
I did try using an Internal Test and Alpha test. But the Alpha version was downloaded to both groups even when only a single group was selected for it.
All the explanations are on this help page
Summary:
you can only have one internal test
you can have multiple closed tests, but users need to opt-in
It sounds like you want to have version 1 on a (new) closed track and will need to get your existing users to opt-in to that, and rmeove them from the internal test
Then have version 2 on a new internal test track that targets group B.
The other option would not be to have an internal test track at all, and have two closed test tracks, one for Group A, and one for Group B.
Internal test tracks are normally for very quick release for developers or immediate QA within your own company. Closed test tracks are usually trusted testers, or for people within your company not necessarily within the development team who can wait a little bit for the rollout to complete.
This isn't really a whole answer to your problem, but I have figured out that you can send people links to download a certain version of the app with 'Internal App Sharing' on the Google Play Console.
So yeah, set up 'Internal App Sharing'. (Sorry, I'm too lazy to write up steps on how to do that.)
After I set that up, when I use the 'App bundle explorer' to observe an apk or app bundle, there is a Downloads tab:
And I copied that shareable link and sent it to my phone. And then I opened that shareable link on my phone. I had to enable internal app sharing in my google play store settings (look this up because it's not obvious how to do it) on my phone. And then the link sent me to a page where I could download that specific version.
Not sure if this type of thing could be used to solve your problem but it's worth a shot.
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.