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.
Related
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
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.
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.
We have a fleet tracking Android app which is isntalled on around 100 mobiles.
Problem is to update each mobile whenever there is a patch release. And unfotunately we have not set auto-update.
Now we need to call each driver and follow the process of update from google play.
This is becoming very tedious as they have to go to google play, search the application and install/update it.
And the mobiles are located all over the country.
Before it was easy as Goolge play was giving an option to know the apps installed on each mobile.
Need your advice on how do we manage/automate this update issue.
Build an in-app push notification that there's a new version and have an easy link to Google Play from it. However, this does have a bootstrapping problem, and you will have to make everyone install the new version manually (as in you call them and ask them to do it) at least once. Still, this is your only viable option, as Google Play developer agreement prohibits pushing app updates through other channels.
If you have email or IM contact with the drivers, you can also send them a message there's a new version with the direct link to the Google Play. They will have to open it on their device, of course.
The link format should be market://details?id=com.mycompany.myapp, https://play.google.com/store/apps/details?id=com.mycompany.myapp, or http://market.android.com/details?id=id=com.mycompany.myapp. Either of these three in general should work, though some OEMs have messed up their devices configuration and prevent Google Play app from intercepting the http/https form properly.
You could check a text file located on a server or something like that and then lookup if the current instaleld version is the same as the server version. If not you could download the new apk and open it. As far as I know this is not allowed by Google Play so you must remove the app from google play
My company would like to give an Android device to a group of our selected customers.
Doing that, we would like to provide users with our mobile app. The app is already on Google Play, but we would like to avoid users downloading and installing by themselves. We prefer to give the device ready, with the app already installed.
We found several ways to manually install an APK on the phone without having to login to the market. But it seems that doing that, the user will not be able to update the app via Google Play, as the app would not be recognized as installed.
Any idea?
As per January 2015, this appears to be impossible. Here is the response I got from Google Play Developer support:
Side-loaded apps do not update via the Play Store. If you would like the app to update, you will need to uninstall the app on your phone and reinstall the app via the Play Store.
I wonder if anyone found a way around this?
To summarize the answer from #Android-Developer and OP's comment discussion:
Google Play recognizes the app signature of APKs regardless of the installation source. As long as you use the same package name and keystore when generating your APK, Google Play will be able to detect newer versions and trigger an update.
To install the app without logging in to a Google account, enable the "Install from unknown sources" option in Settings. You can disable it once the installation is complete.
You may install Titanium Backup if your phone is rooted, then long press on your side loaded app package and select "Attach to market" option. Now you may receive updates via Google Play.
I don't recommend this, I mean never install cracked or patched apps because of copyright or security risks, but installing a Modded version of Google Play can make patched side loaded apps to be upgraded after attaching them to market via Titanium Backup. This is not needed for purchased apps because they are registered in your Google account, so attaching to market will be enough.
To get a MANUALLY INSTALLED APK to show up in the Google Play Store in the UPDATES or INSTALLED section, do either of the following:
1.) Manually install the APK with the SAME APK filename that Google knows the app as (i.e. from the APK download site like APKMirror.com).
2.) If you CHANGED the APK name when you saved it, it will NOT show up in Google Play Store as an installed app.
However, IF there is an update to the app, you will have to do a ONE-TIME search for that app in the store and update it. It will give you the UPDATE option on the app's store page. Once updated via the store, it will show up in the store's Installed / Updates section from now on.
Why does this work? Because the UPDATE will be done thru the store and the APK name it's using during the update process is what Google knows the app as.
If there is NO update, do option #1.
I always add the App name and version info to the front of the filename so I know what it is for later use (because if I'm manually installing, I'll probably be saving it for multiple / future devices).
I also keep the original name at the end, so I can rename it back to the original name if needed. Android is the only O/S I've seen where the filename matters during the install process.