I have setup a compose android app that uses google maps. it works fine requesting permission the first time, but any attempt to run it again I get this error.
Unable to update local snapshot for com.google.android.libraries.consentverifier, may result in stale flags.
java.util.concurrent.ExecutionException: java.lang.SecurityException: GoogleCertificatesRslt: not allowed:
It will run fine again if I wipe the data on the emulator. I know the requests are reaching my google maps platform because I can see the request under metrics.
Related
Got a released app which is using the Google DriveApi (not REST) and it has been working fine for many years.
Started development on next release where I want to use REST. During development I wanted the app to use both APIs. (Eventually I will probably stop using the DriveApi and only use REST.) Implemented first feature using REST. Works fine listing some Google Drive folders using my main Google account.
However, some serious problem occur when I try to use the original DriveApi (not REST): com.google.android.gms.common.api.ApiException: 17: Error resolution was canceled by the user, original error message: INTERNAL_ERROR: null
There's no problem to log-in, but the problem occurs e.g. for a simple function getting the Goggle Drive root folder, and I use the proper scope for non-REST: Drive.SCOPE_FILE
If I re-install the released version from app-store (which does not use REST and never has), I get the same problem! I have a couple of devices which have the app-store version (not re-installed), and the app work fine on these using my main Google account!
Then I created a new Google account, and everything works fine when using this account. I can re-install from app-store and all works just fine.
So the problem occurs when I re-install the app and use my main Google account. Seems like my main Google account somehow got corrupted when I was using REST. But not for the devices where I have not re-installed the app!
I can see these in log just before my app gets exception, but I can see similar logs when all works fine:
2018-11-10 07:56:11.381 1152-1792/? W/AppOps: Bad call: specified package com.google.android.gms under uid 10190 but it is really 10020
Any ideas?
Strange...
After using REST successfully, and getting the ApiException: 17: Error resolution was canceled by the user, original error message: INTERNAL_ERROR: null
when using the Drive API (not REST), do this:
Open https://myaccount.google.com/
Remove the app's access to your account.
Uninstall the app on your device.
Re-install the app on your device.
When you then use the Drive API (not REST) it works fine!.
Try the Drive REST API and you get:
ApiException: 17: Error resolution was canceled by the user, original error message: INTERNAL_ERROR: null
One can note that the old (more or less deprecated) API GoogleApiClient works fina all the time...
Hmm...
Not sure this will help, but for me, I was getting this error with an Android app + the Awareness APIs. I realized I needed an API Key for the Awareness API features (Snapshot and Fence) to work. After I added that, the error went away.
I assume some of the other Google APIs may need that as well in your manifest.
Note: The link is for the awareness API, you would need to check the API guide for other specific APIs.
I'm working on an android device which runs 5.1.1, and it's rooted. My plan is to implement firebase message service in the application I'm building which should run on the device. But initially It didn't have google play services so I installed in manually with 11.7.44 version. But the problem I'm getting now is, it doesn't get the firebase token still; I'm getting the following message:
FirebaseInstanceId: background sync failed: AUTHENTICATION_FAILED
Note that the device is connected to the internet, and also the program runs perfectly on normal android phones.
I'm suspecting whether I should install some other applications in order to run FCM correctly.
any ideas on that?
Thanks.
SO I'm developing an app for android using the groovy plugin.
and I'm facing an issue with google maps where the map loads fine if i set the map activity in the application manifest as the main activity,
but if i set the main activity to be my login screen instead and just go through the application flow, whenever i get to the same map activity, it will not load at all.
and i get the below error in Logcat.
E/Google Maps Android API: Failed to load map. Error contacting Google servers. This is probably an authentication issue (but could be due to network errors).
Give the proper SHA key in the Google console and run time permission for loading the map.
I am trying to create a map app with the GOOGLE API, for use on android devices, but I'm fairly new to this so have been following tutorials to get me started. I fixed my initial problem, however another one has appeared and I can't find what's wrong / how to change it!
When running the app through a mobile, it loads onto the phone fine, a screen loads (the sort of beige colour you see when google maps is loading) as well as the logo and zoom controls. But stops after this and displays the following error in LogCat:
Authorization Failure. Please see https://developers.google.com/maps/documentation/android/start for how to correctly set up the map.
Ensure that the following correspond to what is in the API Console: Package Name: com.example.myapp, API Key: [my api key], Certificate Fingerprint [my code]
Failed to load map. Error contacting Google servers. This is probably an authentication issue (but could be due to network errors).
I have completed the steps on the link and checked my code and made sure all those details match, but it's still not working.
This is probably a very basic error, but how would I go about resolving this / Am I looking in the correct place?
[Code no longer here; had to delete it]
If you run the app through Eclipse with a USB connected device, you need to use the MAPs debug key. If you export the app and load the .apk on a device, that app would have to be compiled with the production key.
Last resort: uninstall and re-install app. Clean and rebuild the project is also a good idea
Moreover, please make sure your API key was an Android key, not a browser or server key. Also check that the service is Google Maps API for Android V2, not Google Maps JavaScript API V2.
If you still get any problems, check your set-up against the top answer in this question: Google Maps API V2 - always get authentication error.
I found a section Crash & ANR in my Google play account
This list the crashes occurred but this is when user report the crash.
I have well managed application but some times it is being crashed as reported by one user.
What i want to get a log from device for the application crashes and save and send automatically.
Is there any Process to get the details of all or Previous Crash from android systems on Next Application Start up?
You can trap and log it manually, but this is usually solved by integrating crash handling and reporting services like TestFlight, New Relic, and other similar services. There are some self-hosted, open source tools like android-remote-stacktrace too.
The libraries are set to capture any unhandled exception your application, log the exception to a remote server so you can view it without requiring the user to send it to you manually, and will then allow the original exception to be rethrown as normal.
Android Handling the Unexpected also covers the idea in detail with some sample code if you really want to do it yourself. That post also lists several more example external services.