I've just put a Bêta APK of my app on the Developer Console. I've also created a Google Group and invited the people that can download the Bêta version of the app.
Google gives you a link in this format :
https://play.google.com/apps/testing/com.app.package
Normally you would give this link to the testers, and if they actually exist in the Google Group they can open it and click the button Become a Tester and would be able to download the bêta version of the app directly from Google Play.
The problem is that some contacts, even though they actually exist in the group and can click on the button Become a Tester... they can't get to the page where they can download the app. A message is displayed saying :
Not Found
We're sorry, the requested URL was not found on this server.
Some users can download the app and others can't, even if they exist all in the same Google Group. Does anybody have any idea ?
I encountered the same issue and it was caused by Google's multiple sign in (on desktop browsers).
I was signed in to my corporate account which I had authorised for testing, as well as my personal account which was not authorised. My corporate account is set as the default account, however when visiting the Play Store it was defaulting to my personal account (maybe because that's the one I use on my Android devices).
The problem can be solved by either authorising all signed in accounts for testing, or by signing out of unauthorised accounts.
Related
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.
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 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.
I am very confused about this, both from the developer site and other similar questions.
I am trying to use V3 in-app billing. Seems to work with the static responses. Want to move on to testing with test purchases using license test accounts.
Basically - it is not working.
A signed app has been uploaded to the developer site (over 6 hours ago), and the app installed on the device, whilst not being signed with the same release key (it's a debug build and key), should work because Android Developers says "you only need to upload your application as a draft application. However, you must sign your application with your release key before you upload it as a draft application. Also, the version number of the uploaded application must match the version number of the application you load to your device for testing". Ie the code on the device apparently doesn't need the same key providing versionCode matches.
My developer console login is - say - a#googlemail.com, and I have a license test address registered (on the developer console) of b#gmail.com. The primary account on my phone is also a#googlemail.com. However I do have a secondary account on there of b#gmail.com. I do NOT want to have to reset my phone and change its one and only account to b#gmail.com.
Android Developers says "The only way to change the primary account on a device is to do a factory reset, making sure you log on with your primary account first" which seems to imply I might have to. It also then says "If the device has more than one account, the purchase will be made with the account that downloaded the app. If none of the accounts has downloaded the app, the purchase is made with the first account" which partially contradicts the first statement. Most of the text on the site appears to apply to pre-V3 code, OS 1.4 etc, so I am not sure how relevant it is.
I notice that Google Play allows me to select the account to use, and both the above show up in the list. Therefore, if I select that second (test) account in Google Play, should that be not sufficient to start testing with that test account?
What actually happens is, whatever account I have selected in Google Play, on starting a purchase I get a message "this version of the application is not configured for billing through Google Play".
Is this because I really do have reset the device and make the primary account b#gmail.com, or because of something else, possibly in the code?
I have some more information now, together with the answer above:
Once I loaded the device with the release signed key the message on a purchase attempt changed to "the publisher cannot purchase own item".
I tried logging in to Google Play with both my accounts and it made no difference. When logged in with the test account I also tried to find the app in the play store. Didn't show up even to the test account (draft app). (I hoped the test account could download it even as draft and therefore following the rules above about multiple accounts I could test purchase with the test account, but no).
Therefore I conclude:
Can only test on a device with an app signed with the same key as the one uploaded to the play store - whatever Android Developers might say.
The ONLY account that can test purchases on a device is the first set (primary) account.
Best therefore to have a completely new account as one's Developer Console account (bit late now).
Would be happy to hear if anyone can contradict the above.
Sign the app you upload to the device with a release key. As far as I know you can't test in-app billing without signing it properly. Actually, last week I tried it as written above and it works.
Hope it helps.
You can have multiple accounts on your devices -- as many as you want. But while testing the app, make sure you don't install it by the app Play Store on your device. Instead, go to Google Chrome, browse to its page on Google Play, and install the app from there. There's a button Install (or Installed).
I guess if you already install the app from account A, then the Android app Play Store will use that account to install next version (or reinstall current version) -- even though you're signed in as another account, like B for example.
However the Google Chrome will just install the app via the current signed in account. This could be a bug and it would be fixed some day. But it's working right now -- when I'm typing this answer. Android team is well known of being lazy for delivering fixes. I hope this "bug" will never be fixed :-)
How to distribute apk to limited users. And they cannot re-distribute to others?
One way to do is get device IMEI number and post to server to check valid user or not. But I am trying to limit in android code itself to avoid server communication.
Also as I will not publish app on google play,I am not able to add Google Play Licence Verification library.
Use Beta-Testing section from Play Store, after uploading your apk on Play Store. You can create a group of user from Google+ and add them in testing section. Follow this :
Create an App
Log into the Developer Console and upload an APK. No need to publish it yet.
Check out the ‘Beta’ tab now, which should show this handy message:
Upload Beta APK
Click the Beta tab and upload the APK again. Publishing from this tab will not push it to the store, but there is a handy button that allows you to promote apps from Alpha to Beta to Prod, which is neat.
Create a Test Group
Using your developer account (it must be the primary google developer account), create a Google+ Community. Public or private, doesn’t matter. (You could use a Google Group too, but Google+ is a pretty good medium for wrangling a beta team, so I’ll recommend it here.)
Add your Community to the list of testers by clicking “Manage list of testers” and pasting the Community’s URL.
Invite Users to Test
Click publish in the Beta tab. Click again on “Manage list of testers” and there you will find a URL to share with your Community. When they go to that URL, they’ll get a signup prompt (later, a play store link). Roll outs will take anywhere from a minute to a couple hours to propagate, as with anything on the store.
Hard code the list of IMEI or device IDs in the app. On launch check the device ID against your white list and either launch or kill the app depending on the result.
You can roll out a version to a limited amount of users through the play store.
Just have to create a google Group or a Google+ group and follow the instructions here:
https://support.google.com/googleplay/android-developer/answer/3131213?hl=en