I have implemented a SafetyNet attest check when launching the app. It works fine when I run the release version from Android studio and detects (for eg.) the emulator from the device correctly. However when I download the same version from the Play store, it fires the failure listener every time, on a lot of legit devices.
It is a restricted API and works fine when run locally on those same devices.
If you check the image, the 33.75% error rate is when I have used this from the play store.
Any idea what could be happening different with the same code when running in app downloaded from the Play store?
Found my issue!
For anyone using 'App signing by Google Play', make sure you add the SHA-1 provided by Google Play to the API restrictions in the API Console.
You should find this in 'App Signing' in the app on the Play Developer Console.
Related
Hi everyone and thanks for hearing me out.
I have an app that I build using Google play games, Google play services, ETC... Basically the debug version works perfectly fine and connected to multiple devices, however the release version can't sign in to google play games and causes the app to crash when attempting to do anything that requires it.
I suspect this is an issue with the authentication, but I tried using the developer console to create a new OAuth2.0 that has the package name and the fingerprint of the keystore that I'm using for release and it still dosen't work.
Thanks in advance for any help!
Most probably it is with the authentication issue . First of all make sure you have the proper release key . This doc will walk you through to get the fingerprint, and then in your google play console under your game services select linked apps and link your release version here
If still doesn't connect to the google play service, please provide your log then I can find the best solution for you
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'm developing an app using Volley to make REST API calls. Everything works great during dev time, but now i put it on Google Play and it crashs when i make this calls.
When i generate a signed apk, put this apk in my device and install it works, but when i upload this same apk to Google Play and install from there, any API call crashes the app. Looking server log it doesn't even hit there!
Anyone knows what can possibly be?
I prepared my own I published in android apps on Google Play. Downloading app. However, I publish every new device is installed after the application version is not automatically updated. I tried on all devices. I activated the automatic update option from the Google Play app.
Unfortunately, I get the same results. Is there that might help?
Solution.
Add validation code inside your own app to check application version and open Google Play if newer is released. You can store version somewhere in your own server.
Automatic application updates are not popular in Android devices. Sad but true.
Do not forget whether your enabled this option in your device https://support.google.com/googleplay/answer/113412?hl=en
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.