101

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'
}
meh
  • 22,090
  • 8
  • 48
  • 58
  • the same with `classpath 'com.google.gms:google-services:2.1.0'` and `compile 'com.google.android.gms:play-services-analytics:8.4.0'` – Alex Zaitsev May 20 '16 at 09:10
  • Have you found any solution? – alex May 20 '16 at 09:45
  • @dit I haven't yet but I think it can related to the new firebase analytics, the app works fine also, there are no issues with any of the google apis just that message. – meh May 20 '16 at 17:06
  • I am not using Firebase but I am getting this issue after recent Android studio updates. I guess it is a bug in Play-services. – The_Martian May 20 '16 at 19:32
  • 2
    I have the same issue after upgrade google play service to 9.0.0. I use Google Map and GCM also. But application works fine – Plugie May 21 '16 at 01:35
  • this google play service 9.0.0 issues – raditya gumay May 22 '16 at 03:42
  • Duplicate of this issue: http://stackoverflow.com/questions/37281942/google-map-api-v2-doesnt-work-since-google-play-services-update-9-0-83 – Jaythaking Jun 07 '16 at 15:51

5 Answers5

177

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.

android developer
  • 114,585
  • 152
  • 739
  • 1,270
Ian Barber
  • 19,765
  • 3
  • 58
  • 58
  • 8
    So it doesn't do anything? We shouldn't worry? – android developer May 23 '16 at 10:39
  • 6
    Shouldn't worry. – Ian Barber May 23 '16 at 18:03
  • 2
    Hi. Is there any link to the bug that we can check? – AL. May 24 '16 at 02:37
  • I downgraded to ```compile 'com.google.android.gms:play-services-gcm:8.+' ``` and start working again. – vrunoa May 30 '16 at 12:12
  • 2
    @ianbarber But this does affect the behavior of my app. It causes my app to go into ANR state. My log console outputs over 100 of this logs which lasts a while...then the anr trace file is written. – box Jun 03 '16 at 14:02
  • I deleted all the saved data from google play services on my phone and the logs aren't displaying anymore. – box Jun 03 '16 at 14:12
  • 3
    It does affect the behavior, when trying to launch an app with gms library included, the startup time is at least 5 seconds, and then that message is issued and then things are fine again. That's pretty close to ANR – Odaym Jun 06 '16 at 13:03
  • 1
    down voted this answer though info is helpful! lol bug I would say – Paresh Mayani Jun 07 '16 at 11:12
  • 1
    Sorry to contradict you @IanBarber but this does impact the app's behaviour the launch time is quite enormous as witnessed by Odaym. And also I see in the logs the presence of Firebase even I've never subscribed to it, that's quite intrusive. – moud Jun 07 '16 at 11:26
  • I'm no longer getting this message after updating to the 9.2.0 library. – RickBoyerDev Jul 10 '16 at 10:01
  • i have version 9.4.52 and i am getting this issue – Aditya Vyas-Lakhan Sep 14 '16 at 07:06
  • still got this error in my logcat and map does't show what should i do?? – Arpit Patel Nov 30 '16 at 11:27
  • Updgrade to the latest version (10.0.1 last time I looked), should go away. – Ian Barber Dec 06 '16 at 06:06
  • I saw this error today and found maps to longer work in our app. Can't tell whether there's a connection or not. We're using maps v2. – the_new_mr Dec 16 '16 at 19:17
  • 6 months later, it is still there... Having the latest GooglePlayServices (10.2.98) so not sure what you meant by "it will be solved in next version". Just a friendly reminder @IanBarber – Ewoks Feb 09 '17 at 18:23
  • @Ewoks are you seeing it at high volumes? If so, could you link log output and note your client and APK versions? Its still harmless, but it would be interesting to see what you're seeing. – Ian Barber Feb 10 '17 at 22:23
  • @IanBarber I am trying to use the latest downloader library and licensing library and found a bug when doing so. Could you please review if my fix is valid? https://github.com/google/play-apk-expansion/pull/1 – jugutier Apr 19 '17 at 22:25
  • these logs are correct, I am facing this issue in android 9 and below. The map is previewing successfully but google map object is not initialized. GetMapAsync never called. Tried every solution. And Map is working fine on Android 10 and above – Bilal Bangash Dec 02 '22 at 06:23
2

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 :')

Filoux
  • 146
  • 1
  • 7
1

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'

JMax
  • 647
  • 6
  • 8
1

  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 .

Shubham Arora
  • 807
  • 9
  • 10
0

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.

box
  • 4,450
  • 2
  • 38
  • 38