Why do I get signature not valid onGoogle Maps Android API?

Question

My app was working fine with position updates on a device with 5.1.

Since then, I made two things: Generating a signed apk. Trying to deploy it to a 6.0 device.

Answer 1

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.

From Ian Barber Answer @ here

Answer 2

Well if I'm not wrong you might have configured some hash key (Shah 1)at Google api console to use Google APIs.

Its working on your simulator or device through debug keystore(its a certificate) because you configured key is debug keystore one.

Now you have generated signed apk and installed, you need add signed keystore Sha1 key to at Google api console.

Story is debug keystore sha1 you can use for development purpose. If generate singed apk file you need it's sha1 separately.