Google Login problem with standalone app

Expo SDK
15

Hey folks - I also came across this issue.

I ran adb logcat with my device plugged into my computer and was able to see the error logs on the standalone app. I got a message that looked something like this:

  E/Google Maps Android API( 4889): Authorization failure.  Please see https://developers.google.com/maps/documentation/android-api/start for how to correctly set up the map.
  E/Google Maps Android API( 4889): In the Google Developer Console (https://console.developers.google.com)
  E/Google Maps Android API( 4889): Ensure that the "Google Maps Android API v2" is enabled.
  E/Google Maps Android API( 4889): Ensure that the following Android Key exists:
  E/Google Maps Android API( 4889): 	API Key: myApiKey
  E/Google Maps Android API( 4889): 	Android Application (<cert_fingerprint>;<package_name>): MY:SH:A1:HA:SH:CE:RT;com.something.myapp

The API key and Bundle Identifier matched what I had in the Google Console, but the SHA-1 Fingerprint / Certificate Hash was different. I changed the Fingerprint on Google Console to the value I saw in the console, and that did the trick.

I was originally getting the Fingerprint with a function like this:
keytool -list -printcert -jarfile growler.apk | grep SHA1 | awk '{ print $2 }'
Per the guidance here, but it seems to produce something different than what I am seeing in adb logcat. I am not exactly sure what’s going on here, but I believe this is where some others like myself are getting caught up.

Edit: To give more clarity, I realize I only spoke to Google Maps. I was also having an issue with the Google Login, and it was also remedied by changing the certificateHash/fingerprint in my app.json and Google Cloud Console.

1 Like