I recently published on android app on the playstore and I had no problem or warning.
Although, people can't download the app because I had activated the "pre register feature"(without knowing what it was ....) and thinking It had no impact.
It looks easy to deactivate the feature on the play console developer dashboard, but every time I try to deactivate it, I am getting this error message :
"An unexpected error occurred. Please try again later. (668269003)"
I have successfully checked the "inactive" box all the countries but one hoping it will solve the issue but for now, I still can't download my own app.
Should I just wait and try again ? Any ideas ?
An other idea I had was to change the "Launch deadline: Nov 4, 2019" in order to make it shorter so that It would solve my issue, but I have no idea how to change that deadline date.... (I don't even remember seing that date when I uploaded my package on the store)
thanks for any help.
I received the same error #668269003 when trying to disable pre-registration for an app that I was trying to publish to the Open Beta track. Before disabling pre-registration, the console indicated that the Open Beta should be available and should override pre-registration for the pre-registered countries when using the SYNC WITH PRODUCTION setting.
To work around this, I did the same as you and disabled all but one country (not my country, or the countries I'm actually interested in for now) in pre-registration, which does appear to save without the error.
From there, I went into the release track for the release I'm interested in (in my case, Open Beta), and selected CUSTOMIZE AVAILABILITY and manually ticked the countries that used to be enrolled in pre-registration.
After saving and letting the Google server pixies do their "processing update" shenanigans, the app finally showed up with the option to install rather than pre-register.
I've opened a request with Google, if in the unlikely event they get back to me for some reason I'll update this reply.
I assume that these steps should also work for the production track, but I'm not yet in a position to test there.
Note that the launch deadline is the date you enable pre-registration in a given country, plus 90 days. I don't believe it is editable.
Similar to #repentspinner, with the new google console I was able to enable pre-registration for a small country I didn't care to release to, then I was able to disable it for the actual country I was targetting. This triggered a review process which took <24 hrs. Once past review the app now shows 'install' as expected.
I just went live with my android app (Xamarin) -- and all my users are getting a -504 error when they try to install the application. Please help!
The app name is 'ControlTower' (the one with a tick symbol); can you tell me what I might have done wrong
Seems to download fine here. So I don't know who "all your users" are, but they might want to check this link: http://appslova.com/fix-android-504-error/
The error 504 code appears while attempting to download apps or games
in the Google Play Store. This is a gateway timeout error and is
generally associated with slower internet connections or mobile data
networks. Simple fix that worked for some is turning your mobile data
off and then back on. You can try it now by turning your Airplane mode
on and then off or by going to settings >> data usage>> turn off
Mobile data and turn it back on. Now try to download or update the app
via Google Play. If that didn’t work, some users have even solved the
Google Play Store error 504 by freeing some space in their android
device by uninstalling unwanted apps or games. If these Android fixes
didn’t work there are more to go in this post for “App” could not be
downloaded due to an error. (504)
Has more to do with the user's device than anything else. You say it just went live. It might have to fall through to all proxies and servers etc. So it might just be a small hiccup while going live on the app store.
Did anyone got this error?
It seems, clicking any button in my android application and at the same time Google related error message is occurred.
Google related error messages like,
“The process com.google.process.apps has stopped”
Or
“Google Play Services has stopped”.
I tried in emulator and my mobile, even tried deleting it and adding a new one, still i got the same message.
Please Advice...
This error usually comes up when you are making some changes to the settings of the Android Operating System. You may refer with this article on How To Fix ‘Google Play Services Has Stopped’ Error On Android.
emptying the cache of the system app Google Play Services.
reset the app preferences
add your Google Account Once Again
reinstall Google Play Services
clear the Google Service Framework cache
However, if none of this works, you may want to consider checking this another blog.
I have a problem with updating an Android app. My requirements to the application are:
It must work constantly (24/7);
Updating should also be automatic, with no user input.
I uploaded the application to the developer console to conduct beta-testing. Then, I installed it on the tablet (I used URL).
Then, I uploaded the update, but the application does not start the updating process automatically.
There are no added additional permissions. The "automatic updates" are turned on in Play Market settings.
4 days have passed. If I go to the app's page in the market, I see that an update is available, but it does not start the download process.
The question is: what may be the problem? Why does the app not update?
Is it possible that the app gets reinstalled instead of an update (thus requiring some user input to proceed)?
Thank you in advance!
in Google play store app, open side menu, go to settings, enable auto update apps. It should do the trick
The Google Play auto update solution does not seem to work, when the app is always running. The way to achieve it through enterprise management tools.
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.