GoogleSignatureVerifier signature not valid message (google play services 9.0.0)

AndroidGoogle Play-Services

Android Problem Overview


I have recently updated to the google play services library version 9.0.0, and I keep getting the following logcat message:

05-19 23:07:30.023 19237-19508/? V/GoogleSignatureVerifier: options.developer.com.developeroptions signature not valid.  Found: 

While my app isn't using the google maps api but it is using the analytics, ads, and google plus apis.

The only mention in the documentation regarding the usage of the api key is when using google maps, or android places api.

I have also tried adding the 'com.google.android.geo.API_KEY' with a correct key but it didn't help.

here is my gradle.build file:

apply plugin: 'com.android.application'

android {
    compileSdkVersion 23
    buildToolsVersion "23.0.3"

    defaultConfig {
        applicationId "options.developer.com.developeroptions"
        minSdkVersion 9
        targetSdkVersion 23
        versionCode 23
        versionName "1.06"
    }
    buildTypes {
        release {
            minifyEnabled false
            proguardFiles getDefaultProguardFile('proguard-android.txt'), 'proguard-rules.pro'
        }
    }
}


dependencies {
    compile 'com.google.android.gms:play-services-plus:9.0.0'
    compile 'com.android.support:appcompat-v7:23.2.0'
    compile 'com.google.android.gms:play-services-analytics:9.0.0'
    compile 'com.google.android.gms:play-services-ads:9.0.0'
}

Android Solutions


Solution 1 - Android

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.

Solution 2 - Android

You will find a lot of solutions on the net, but the only one who works for me was to downgrade the Google Play Services to 8.7.02 version on my devices. I hope Google will fix this error rapidly :')

Solution 3 - Android

As mentioned in the other answers, its the Google Play Services 9 update to the device. You can have these options until google fix the bug:

  • Safely ignore it

  • Downgrade your phone/device using Settings->Apps->Google play services->(three dots on top right menu)->Uninstall

    If the Disable/Force Stop buttons are greyed out you may need to remove the app from being a 'device administrator' before uninstalling it.

Google plus blog relating to the bug: https://plus.google.com/+ChristopheBeyls/posts/LC2XCSoaVBJ

Removing/Recreating the keystore.debug file is unlikely to help. If you've done this already then you'll need to create a new one using the 'map api developer console'

Solution 4 - Android

  1. make sure you entered your SHA sinature and package name correctly.

  2. make sure you have enabled your GoogleMaps Api in your ApiManager>Overview after creating your project in api console(search it in google)

  3. make sure you have allowed internet permissions in your manifest file

  4. in your build file use compile 'com.google.android.gms:play-services:9.0.1' (works for me)

In my case i missed out step 3 .

Solution 5 - Android

I had to update the gms library to 9.0.1 and delete all the saved data from google play services on my phone and the logs weren't displaying anymore. They were causing me AND state in my app before, which was giving me major headaches why this was happening.

Attributions

All content for this solution is sourced from the original question on Stackoverflow.

The content on this page is licensed under the Attribution-ShareAlike 4.0 International (CC BY-SA 4.0) license.

Content TypeOriginal AuthorOriginal Content on Stackoverflow
QuestionmehView Question on Stackoverflow
Solution 1 - AndroidIan BarberView Answer on Stackoverflow
Solution 2 - AndroidFilouxView Answer on Stackoverflow
Solution 3 - AndroidJMaxView Answer on Stackoverflow
Solution 4 - AndroidShubham AroraView Answer on Stackoverflow
Solution 5 - AndroidboxView Answer on Stackoverflow