I am trying to test google play services features in an app, without publishing the app.
I went through the below link to do that.
https://developers.google.com/games/services/console/enabling
This process worked earlier but i think it has changed now, as i am getting the following error even after checking all the steps mentioned in the link above.
"The application is incorrectly configured. Check that the package name and signing certificate match the client ID created in Developer Console. Also, if the application is not yet published, check that the account you are trying to sign in with is listed as a tester account. See logs for more information."
Does anyone know if there has been any change in the process or if i am missing out something? Thanks.
You need to publish the app before it becomes available for testing.
If you publish the app and it is only in the "alpha testing" section then it is NOT available to general public; it is only available to activated testers in the alpha section.
EDIT: One additional note: "normal" uses will not find your app on Google Play, but also the activated tester can not find the application by using the search box.
Only the direct link to the application package will work (only for the activated testers).
You do not need to publish an app for testing. From the error it seems that the users/testers who want to test are not white listed. Quoting from the official documentation.
If your game is in an unpublished state, you must whitelist the user accounts that you want to grant access for testing. Otherwise, your testers will encounter OAuth and 404 errors when attempting to access the Google Play games services endpoints. Also remember to add yourself as a tester, or the Play Games SDK will not work for your user account
Hope this Helps!!
I integrated Google IAP Billing to an Android application.
I published my application in Alpha version on Google Play Store. I copied the public key that I added in my project on Android Studio. So, I use the good Public API Key with my IabHelper instance.
I signed an APK that I use on a device with an unique account that is different from my developer account. This account is added in the license testing emails field on the Settings part of Google Play Developer Console.
I also checked the SKU ID of the item I want to purchase is the same on my application and on the application signed.
When I launch the buy process, I get a dialog with Please sign in to your google account error. But, I am already connected because I can go on Play Store application and download apps. I also tried to clear cache data for Play Store app and Google Play Services but nothing works for me.
I must mention that on the manage list of alpha testers, I have created a google+ community like asked but there is no link to send to my alpha-testers to opt-in.
Someone has an idea about the problem ? And the solution to solve it ?
The alpha tester has to satisfy these two conditions:
joined the alpha testing community
opted-in for alpha tests
Firs you have to invite the tester to the alpha testing community. Second the alpha tester have to opt-in using this URL: https://play.google.com/apps/testing/your.package.name
It just takes time. Give it couple of hours and it will work.
Also make sure that the file you are running on your phone is signed with the sane certificate that is uploaded on google play (not debug file)
I´ve succesfully implemented a purchase flow for my app.
My app is published in Alpha stage with two of my google accounts listed as testaccounts. The APK published is the same installed on my phone.
Though, when I try purchasing something I get the "Authentication is required, please log in to you google account".
So what I did was 1. removed all my accounts on my phone and re-logged them. 2.Cleared all the data of the Play store. 3.Uninstalled the latest update(Incase it was the new update playing fuzzy).
Still the same error.
Someone that can help me? Really dont want to release the app without testing the purchasing..
Thanks in advance!
If I remember correctly, I got rid of this message by creating Google Group (https://groups.google.com) and adding my test accounts there. Then go to Google Play Developer Console, Your app -> APK -> Alpha testers and choose "Manage list of testers". There, add just created Google Group, and share a link to your app (appears below) with your test account. Next, open that link from email on your test device, and follow instructions (you will need to login in Chrome on mobile).
For reference:
I am confused about android application testing. when I publish an alpha version, do all the people who are registered as testers in the whole world have access to the app or do I get a link and send it to whoever I know to test it. if its the latter how can I get testers for my app.
Alpha and beta tests are working in the same way. You upload your app to google play, fill out all the fields in your store entry and then you need to create a Google Plus community. Copy and paste the URL of the community into the Google Play developer console as testers, you will see another URL2, this URL2 has to be opened by your testers. Now you need to find people joining your group in Google Plus and tell them the procedure for tester:
Open URL2
and confirm to participate the testing
The installation has to be started with a browser, the URL of your app is the same as for apps in production.
If you ship a new alpha version, your testers get the new version automaticly if they have configured that.
From here on everything is as it is for apps in production.
I agree it is a kind of an odd procedure and I hope I explained it clear. However, what you can always do, just upload your apk to a web server and provide your testers with the link for the app on your webserver, your testers only need to accept installations from third party. You can't get ratings for such an app.
Later what you said only will work out in alpha testing, you should have separate testing team in your organization so that you can share the URL with them to test the app or you can add them using their google play account so that the app will be visible only to them in their Google play app, not to all of the real time users.
Until you upload the apk in production mode, your app will not be visible to other users.
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.