I just finished the first version of my react native app and I've uploaded it to the google play store for open testing. However, I can't get a public link that anyone can download the app from to work.
I have used internal testing, closed testing and they both work ONLY IF I have testers added by email to my list.
The two links that are available from under the testers bar in Open Testing are "Join on android"
https://play.google.com/store/apps/details?id=com.(Myapppname)
as well as "Join on the Web"
https://play.google.com/apps/testing/com.(Myappname).
The first link ONLY works if I am logged on to my main account (it shows "We're sorry, link is unavailable...etc)
and the second link says that the app doesn't exist or I am not added as a tester - but open testing should work without me manually adding new testers right?
I would very much appreciate any help on this.
Extra info:
App is "under review"
App has been uploaded today morning (been 9 hrs+ since uploading).
probably the open testing version is under review.
you can check this out from Google Play console, from "Releases overview" in left menu.
just wait (it may take couple of days) and then it will work just fine.
Related
I have an app that already have had several releases pushed to the Open Testing track:
The earliest release was 22 hours ago and the latest, 2 hours ago. However, no one seems to be able to access the app with either links provided here:
The first link for joining on Android shows this:
The second link, for joining on the web, prompts me to sign-in to my google account, and then shows this:
However, people that were originally in my internal testing email list can access the app from the first link, but not the second link. I am also able to download, install and run the app from the first link on my Android Emulator (using my own google account which is in the internal testing email list).
I've tried adding new users to my internal testing email list, but that didn't allow them to access the Open Testing release.
I've also tried pausing the internal testing track, but that did nothing. I have read elsewhere that the open testing app will only be available after a few hours, but the first release has already been released 22 hours ago.
How do I fix this?
If you see there it says "In review", you should expect them to review and approve it since there are many cases of misuse of apps in the Play Store.
You can see the status in "Go to Publication Summary":
I have cloned the project from https://github.com/actions-on-google/appactions-common-biis-kotlin. I made the package name of this project the same as my draft project in Play Console which has a temporary app name 'com.acesoft.actions (unreviewed)'. I can trigger the app actions with App Action Test Tool (AATT). If I set the Invocation Name to "test app" with AATT, it would work on my physical test device if I say "Open active tasks in test app". However, Google Assistant would not open the app when I say "Open active tasks in todo". Todo is the display name for the app. According to the documentation, the default invocation name is the display name of the app. The command "Open active tasks in todo" would result in a search in the web. What did I do wrong? How do I invoke the app actions without AATT?
I have also tried typing the following in Google Assistant:
"open active tasks in todo"
"open active tasks in actions" ("actions" is the last part of the temporary name)
All these commands would result in web searches instead of opening the app!
Can anyone help?
If your app is not published on the Play store, it definitely will not work. Google Assistant only formally recognizes apps that have been uploaded and have passed review. It works in the test tool because that tool establishes a temporary "preview" of how things will work if it were fully published.
Still, in some cases, Google Assistant is unable to match the name of the app as spoken to the name of the app as installed on the device. This situation is not possible to resolve on your own. What you will need to do is contact Google Assistant support and explain what you are trying to do. They might be able to make a change manually to the backend to enable this.
You can see someone else having a similar problem in this public bug. However, please do not file a new bug, and do not fill out the form unless your app is uploaded to Play. If your app is uploaded to Play, follow the instructions given in the last comment on that issue:
If your app is shipping on the Play store, then you can get support for this using this support form - you should choose "App Actions review" for now, and point out that you would like a manual mapping for your app. Don't worry about the actions console project ID - that is for another project.
For me it was enough to put my app into "internal testing" in the Play Console and then install the app on device through the test link that is provided by the Play Console. I could use Google Assistant and use the app name for invocation.
I published my app in internal app sharing. After I shared link to download to myself, but to another account. I turn on internal app sharing in Google Play on my phone. When I click downloading, I catch error -> Error retrieving information from server. DF-DFERH-01
I tried to test in two phones, but with same google account.
There is a step I missed - testers have to opt in to the test program before they can use the shared link, and until they do they get the opaque DF-DFERH-01 error. On the Play Console under Release Management, select App releases. In Internal test track, click Manage. Under Manage Testers click the drop arrow. This opens up a panel, and near the bottom is an opt-in URL. Copy this and send it to testers. They have to click on this link and agree to opt in to the test program. They can then download the current version. After this they can also use internal app sharing links for new builds.
In my case, I was trying to access the internally shared debug app not a production testing app. For this, I was using Internal App Sharing feature. To be able to install and use such apps one's email needs to be added to an email-list(as per the settings we had) otherwise, anyone with the link can install.
Problem
The problem is despite having my email in the list, and email representing a google account I was not able to install it. I faced this error.
Click here to see the Screenshot
Cause
I maintain about 8 google accounts on my mobile and I was logged in to all of them. I realized having multiple accounts is causing the issue.
Solution
Instead of logging out from all the google accounts, I simply created a new user in my mobile and set it up. Then I opted-in to Internal App Sharing in the App store. Then shared the app link via google-keep. Voila, I was able to install it.
In my case I just had to wait ~48 hours and it Just Worked with no other changes.
A few more silly things to consider if you are new to Google Play Console.
You need to make sure to enable Internal App Sharing on Google Play Settings, here is a tutorial for that.
Do not forget to publish your modifications by clicking on publication overview (sorry for the Portuguese language on the pic, but you can find through the icon):
And then publishing it by clicking on the blue button (publish modifications or something like that):
After doing this, try to clean the cache of your play store and remove all updates from play store (after doing this you'll need to enable Internal App Sharing again).
I was able to get rid of the error by clearing the storage of the google play store app then open the play store app again and enabling the internal app feature then opening the internal app sharing link again.
sometimes if that didn't work , restarting the device does the trick!
I was trying to setup Google Play Leaderboards in my app, by following the instructions on googles website.
I created a Leaderboard for my app (not submitted yet).
Downloaded the "Android Basic Samples" code from Github, and copied the four source files "BaseGameActivity","BaseGameUtils","GameHelper","GameHelperUtils".
Updated my AndroidManifest.xml, strings.xml, ids.xml and build.gradle
In my app activity, I changed the class to extend BaseGameActivity.
On launching my app, my app immediately tries to sign into google play or something (it shows a Google Play Games Logo "connecting to"), and then shows a message
"Create a profile. Unfortunately, Google+ couldn't set up your
profile. Try again later."
If I click on "Done", then Google Play Games prompts me to choose an account. So I click on my developer account (the other option being to create an account), and the same thing happens again (It shows the google now message)!
I've never created an Android App before, or used Google Play before, so all this is new to me. How should I fix this ?
EDIT: If I just click outside the "Google+" dialogue box, then it disappears and my game starts. Likewise in the loop if I press "cancel" when it asks me to choose an account, my game starts. But I can't test if leaderboards is working then! How do I fix this ? Why do I need a google+ profile ?
EDIT: And why is it having trouble setting one up ? Is there some setting I need to use to disable Google plus? I am using Android 4.4.4 and android-10, Google Play Services 7.5.0
You should try logging in to your g+ profile before starting the game. The problem is not with your app, but with how the leader boards are authenticated. Hence why g+ is needed. : )
Edit: If the above fails, I would try to recreate another g+ profile. And if that fails, contact the play team at: https://support.google.com/googleplay#topic=3364260&contact=1
Best of luck!
I have published my app for alpha testing, but not able to download it from play store.
I have opened the url "https://play.google.com/apps/testing/com.*" and accepted to be a tester and now it shows me "you are a tester". But when I click on the link "download it from the Play Store", it shows me "Item not found" in my test device play store and "requested URL was not found" in desktop browser.
App is in published state for more than 48 hours.
App is published in all countries.
google groups for testers are added, I can see the group in manage testers tab. Tester account is added to the group ( triple checked it)
test device has only one tester account.
I can access the in-app purchases, which means the app is published properly. Google doesn't support draft mode anymore.
I went through some similar posts in stackoverflow, but there is no definite answer. Looks like for some people it resolved automatically and some people are not lucky enough.
If the app is "Published", but when you click in "View in play store" the site (example: https://play.google.com/store/apps/details?id=com.companyname.appname) show the error:
"We're sorry, the requested URL was not found on this server",
try this:
In "Google Play Console" (https://play.google.com/apps/publish), select your app
goto menu: Release management / App releases
In Aplha, click in the button "Manage Alpha"
Click in "Manage testers" and copy the link "Opt-in URL" (example: https://play.google.com/apps/testing/com.companyname.appname)
Send this link to your alpha users, you and the users need to click in "Became a tester" before access the app in PlayStore.
After this, open the link of app in play store again (View in play store) logged with a user from the testers list.
If the url still don't open, try close your browser, or clear the browser cache and try again. The browser store a cache of redirects.
If you are using Chrome, then it caches redirects. To fix it, clear browsing data. More details on this
In my case, the issue was that I wasn't logged to Google with the proper account in Chrome.
I cleared all browsing data, but un-logging from Gmail/Google and re-logging with the proper #gmail.com account would probably have done the trick.
Another thing to check is whether or not Pricing & Distribution -> Only make this application available to my organization is checked. It seems that this doesn't interact well with Alpha- or Beta-only tests, even if your test account is in the given domain. Once I turned this flag off, my beta-only app became visible via the Play Store link from the testing signup page.
In addition to all the great answers here, I just found out that if you did an internal test before the closed (alpha) test, the Play Store may want you to use the internal test URL instead.
So say you have your great app and you released it to the internal test track. You created a list called "Internal Testers" for that track and it all went swimmingly. When you did this, Google Play gives you a URL for those testers of the form https://play.google.com/apps/internaltest/{id}. Your internal testers joined the program using that URL, downloaded the app no problem and the test went through.
You now upgrade to the closed track (alpha testing). You create a new list called "Alpha Testers" with new people in it and you enable your release both for "Internal Testers" and "Alpha Testers" thinking that you should carry over your internal testers to alpha. When you do this, Google Play gives you a URL of the form https://play.google.com/apps/testing/{package}. Your alpha testers can now join the program using that URL and download the app. But your internal testers have to keep using the internal test URL to join the program.
From testing a variety of scenarios, it looks like moving a tester from on list to another doesn't fix the problem.
As far as I can tell the Google Play documentation doesn't mention any of this.
Where you add groups for test - there have a link for tester (something like terms) you need to click this link on each testing device and say "Yes"
After that link apear in market. I wait 3 days before found it : )
For my part it was due to the fact that I sent the link through SMS. It worked when I sent it by email. This link has the form https://play.google.com/apps/testing/com.*. This is this link that you have to share by email.
This can be due to a silly mistake where you aren't signed in with the appropriate Google Play account in your device's Google Play Store.
Sign in with the testing gmail account into Google Play and then click on the test-link
For more detail check Item not found
allow access to
Settings -> internal access -> Manage users with download rights later
Settings -> Internal Access -> Testers
and the app link will work
I had this similar issue.In my case, I had multiple testers as CSV and there was an space between multiple users tester.Space was the issue in email address.Bad email address may cause this problem.
Also, make sure the device you are using is among the supported devices for your app. For this, check Release management -> Device catalog on play console.
If this is the problem, expect to see a warning similar to the app is not compatible with your device when you visit play store page via a web browser and Item not found error via play store app.
In my case, I had to make some changes in the Manifest to correct the list of supported devices. So, I replaced below line causing the number of supported devices to be 0:
<uses-feature android:name="android.hardware.camera2.full" />
with:
<uses-feature android:name="android.hardware.camera2.full" android:required="false" />
In your case, Manifest may need a different change of course.
In case someone has tried the several suggestions and has not worked, I want to share another situation I haven't seen listed anywhere else.
Make sure the latest build uploaded is not deactivated. The Play Store console doesn't warn you if, for any reason, the release is made unavailable to your testers. It'll show with a greyed out row, like this:
Check on App releases > Manage, in you track dashboard, that the latest build is Added, not Deactivated.
In my case is Android Studio emulator, I relaunch play store after few minutes googling, then no more such error "Item not found".
In my case the emulator had been started a couple of months ago and perhaps cached something wrong.
I kept receiving BillingClient.BillingResponse.ERROR resulting in this message.
After restarting the emulator it started working again.
Simple way is to use incognito mode. Thats it.