I uploaded an app I developed to google play. Since the app isn't free, google doesn't allow me to download it to my device.
The first users who tried to download my app claimed they got the 505 error (by leaving their comments on google play).
I read some threads about this error here on stackoverflow and made some changes that hopefully fix the problem, but how can I check it myself? Do I need to use other people's devices and pay each time I want to check if my app is downloadable or is there a better option ?
thanks
edit: just to be clear - I'm looking for a way to see whether people can download and install my app without getting any error messages. Preferably by going to the google play and downloading it myself.
The app itself works great once it's downloaded and installed. The problem was that people couldn't download/install it on their device.
You can use Google Administration to check erros and statistics for your apps.
Login to your Google Account on this page:
https://play.google.com/apps/publish
There you'll find all your uploaded apps. You'll also find crash reports, etc. Just for better administration of your apps.
To test your app the best way is to use the debug or Run 'app' option in Android Studio. If you want to test the signed apk you can also build it inside Android Stuido with the Build -> Generate Signed APK option.
Or you use the console commands if you don't use an IDE.
Check the documentation of the ADB (Android Debug Bridge)
http://developer.android.com/tools/help/adb.html
I hope this helps.
Related
I used to test migration problems via installing old APKs from google play console and then updating to the most recent internal test version.
Since at least a week this doesn't work anymore. Every share link to a specific APK just links me to the latest APK that is published. I'm talking about this share link:
So either the live production version, or as an internal tester the current internal test version.
Anyone else has this problem? I couldn't find anything about it online.
My personal fix now is to manually download the APK, install it via ADB and then update via playstore. But that's of course more annoying than just clicking a link.
I have been in contact with an agent from google for more than 1 month about this issue, first they insisted that it was not a problem, but I helped them to understand this issue with a few images. The agent who took care of me says that their technical team has been investigating this issue for a while.
It seems we have to wait until we get a proper fix. Until that, you can use this area to upload your apk and get a specific link for that:
https://play.google.com/console/u/0/internal-app-sharing
This part gave google play link for that build and still working on android devices without a problem.
Best!
I have a problem in an app updated in play store.
Around 800 user could updated it without problem, but we have 3 users who get this message:
I've try install it with apk instead play store, with a similar result:
The min SDK is 16 and the SDK target is 28, and this devices have SDK 27 and 28.
One of these users had a device in which she couldn't install it. But last week buy new device, and she can't install it too. This new device has never had the application installed before.
How can I see any information about the problem?
I had such a problem, when tried to install a new version of my app. I found the reason for the problem when installing the new release version of my app using Android Studio. The error message has explained in detail what the problem is.
So if someone has such a problem I would suggest getting a device on which the error can be reproduced, then trying to install it using Android Studio and check the message.
The full story in my case was as the following: I had two different applicationId for "release" and "debug" configurations. In the new version of the app, I added a "provider" to the manifest. During my development I installed the debug version and then I deployed the new version to the Play Store. When I tried to install the deployed app on this device I got the message that it cannot be installed. The reason was that the release version had the same provider as the debug version, so they cannot be installed both. The solution is to change the authorities of the provider according to the applicationId.
This looks like a problem on the device, rather than a problem downloading from Google Play store. Logs from this should be in the users device logs, like you get for your app. You can ask your user for the logs, by asking them to send you a bug report. There are instructions here on taking bug reports.
When you look at the bug report, error messages from the Play store are tagged with "Finsky". You may also see errors from the device package manager.
When errors like this occured, it is recommended to read the link (see common ways to fix the problem). Most of the time cleaning Google Play Services cache and data will do the trick:
Clear the Google Play Store cache
1.Open the Settings menu on your device.
2.Go to Apps or Application Manager. (This option might differ depending on your device.)
3.Scroll to All apps and then scroll down to the Google Play Store app.
4.Open the app details and tap the Force stop button.
5.Tap the Clear cache button.
Repeat the steps above, but replace Google Play Store in step 3 with Google Play services.
Try to download the app again.
Clear the Google Play Store data
If cleaning the cache of the Google Play Store and Google Play Services doesn't resolve the issue, try clearing the Google Play Store data:
1.Open the Settings menu on your device.
2.Go to Apps or Application Manager. (This option might differ depending on your device.)
3.Scroll to All apps and then scroll down to the Google Play Store app.
4.Open the app details and tap the Force stop button.
5.Tap the Clear data button.
6.Clear data button
The day before yesterday the application in which I work could be installed without errors in all the devices with which we work
Yesterday in some devices came a message from google play protect saying that the app was dangerous but allowed to install it
Today suddenly there is only one error saying that the app was not installed. And to install it you have to disable Google Play Protect on all test devices
The only important modification I can think of is that yesterday I had to format my computer installing unity 2018.2.6. The previous version was 2018.2.5
The app is not yet published and we are testing it by copying it by USB from device to device
Anyone know if there were major changes in Google Play Protect in the last few days, and how can I implement them in my APK to comply with the security guidelines and avoid further problems when publishing the App in the Store?
you can test two way to resolve this problem:
1- change your sign and fill all fields in sign maker form,
2- contact with google play protect team and report this problem to them, you can use below link:
https://support.google.com/googleplay/android-developer/contact/protectappeals
after one or two days test again and try to install your app,if protect team resolve that problem you can install app without any dangerous message.
You now (Android 10? and upwards) need to go into Settings > Security > Google Play Protect > Gear Icon (top right) > Turn off toggle.
Then you'll be able to install your APK. Be sure to see it's Information/Details and manually grant each permission that it may need.
My app uses AdMob. My app doesn't contain any inapp purchases. No device is excluded in developer console and devices tested had higher sdk version than minimum required. My app is optimized with proguard and then zipaligned. Users can install other apps without problems. Why are they getting this error? How can I solve it?
Also when trying to install it via browser on a PC? In this case, where does the error occur, on the pc or the mobile device?
Which app is it?
I think Google Play takes random amount of time even after app being published, before it becomes available for download. Same thing happened to other person I know. After few hours of app being published (not app being uploaded) his app could be downloaded. His app could be downloaded before mine even though mine app was uploaded before his.
I have some functionality for rating my app and for viewing/installing other apps I have on the marketplace that I need to test in the android avd emulator. To do this I need to have the latest google play apk installed but I am unsure of the official location to download this from so I can install it on to the emulator.
Lot's of the sources I have found are for file sharing sites and out of date apks and I would be grateful for a link to the official apk. For some reason best known to themselves I don;t seem to be ble to get it from the main google play site. this is most confusing!
Or is there another way to test market app functionality on an emulator?
what you are looking for is: "market://details?id=" + APP_PNAME
I strongly recommend using the android code snippet app rater
good luck
First, this is not a programming question. Second, there is no such thing as an 'official download location'. The Play Store application is only available on licensed devices. Even if you pulled the apk from your device, it won't run on the emulator as is, since it requires other components as well. So, test on a real device if you need access to the Market/Play store.