Google Map Api v2 shows “V/GoogleSignatureVerifier : signature not valid” error message in log

Question

I am developing an Android application using google map api v2 to show a Map in a Fragment. When I run the application, I always got this error message poppin i

Answer 1

By checking the internet for the other people who encountered the same problem of yours, in updating Google Play Service to 9.0.83. I found a discussion here on how to solve that problem. You can try to check it, if it can help you.

Some solution is by checking if you have enabled offline work for gradle, deselect Offline Work if it's checked. Then, confirm if you have latest version of Google services mentioned as dependencies in project level build.gradle: classpath com.google.gms:google-services:2.1.0. Clean and build the project after the gradle sync completes.

Try to update the SHA1 key in your project on Google Developer Console and update the Maps API key in your android project.

Also, some people fixed it by just deleting the debug.keystore file found in the android folder.

Answer 2

I have fixed it by deleting the debug.keystore file found in the .android folder. It will generate automatically and create new SHA1 using that file.

Answer 3

you should change Map api v2 to v3 :- Map API V3 coz of Version 2 of the Google Maps JavaScript API is no longer available. This guide is intended to help developers who are already using the Google Maps JavaScript API v2 migrate their code to version 3.

Answer 4

Gnah. This was bugging me for hours! Just deinstall the updates of Google Playservice 9.0.83. Version 8.7.02 is working here. Also keep this posting in mind: https://plus.google.com/+ChristopheBeyls/posts/LC2XCSoaVBJ

Answer 5

As per Ian Barber's comment in this answer Google Play services version 10.0.1 will fix this issue.

Updgrade to the latest version (10.0.1 last time I looked), should go away.

Hope this will help you.

Happy coading!!!

Answer 6

Apparently it's a known issue acknowledged by a google developer stating this in a more recent post:

Sorry, thats a bug! It's just spurious logging though: Google Play services does some checking to see whether you are a Google app or a regular third party one.

As part of that, it calls the signature verifier and the logging ended up more verbose than intended - it will be fixed in a future version.This shouldn't affect the behavior of your app at all.

So it should just be ignored until the future update...