Running app from Android studio on my device for testing is working fine. But when I am trying to install same app from Google Play, which is published under beta version getting error. I have uninstalled unsigned .apk from the device but am still not able to install from Google Play.
Even cleared phone cache same result.
Sounds like an error with the Google Play Store.
Go into your app menu, force stop the Google Play Store Service, Clear Data, log back in and try again.
I was facing with the same problem. It was happening in my case was because google play has conflicts with already installed version of another app with MAP_RECEIVE permissions. I don't know why. I wrote that a lot of peoples faced with the same problem with some kind of FACEBOOK permissions as well. But in my case I was't able to install release file as well and I was reading in adb logs what exactly happening.
I added {applicationId} in AndroidManifest.xml
android:name="${applicationId}.permission.MAPS_RECEIVE"
That helped me.
I think there is no issue with your code, you have to remove the google account from your device and clear the cache of google play services and google play store. Then restart your device and login with your google account and then try to install the application.
if this solution not working for you then there some issue with Marshmallow.Because some application not compatible with Marshmallow.
Related
When we try to install the .apk which is signed by putting it in file manager of the phone and not published on playstore, we get an issue ,
"Play Protect doesn't recognise this app's developer. Apps from unknown developers can sometimes be unsafe."
By clicking on "Install anyway", we are able to install the apk, but we don't want that pop up to come.
We need to preload the apk on a phone without publishing it.
We have done it in debug mode and face no issue, but when we did it in release mode and signed it, the issue arises. Also, from second time onwards, the issue is "App not installed".
We have seen all the solutions around the web in stack overflow, found a link to be similar, but the issue is different here. Since we do not have to publish it in the Google Playstore but preload on a phone, so the solution of publishing the app to not get this Play Protect issue will not work.
Expected : Play Protect block issue should not appear even if we don't publish it in Google Playstore.
Actual : We are facing Play Protect block issue when we signed the app and trying to sideload/preload the .apk .
You can disable Google Play Protected form Google Play store and it will not ask anymore. Hear is the link that shows how to disable play protected,
How to disable Google Play Protected?
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.
There is the following problem: there was some application on Google Play, it worked good. I added one feature and ProGuard protection and uploaded a new version on Google Play. Some users downloaded my application and it didn't work for it, but some of them deleted it and installed again - it worked! May it be problem with Proguard or not? I don't understand why it happens. Thanks in advance.