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 in my log every now and then.
我正在使用谷歌地图api v2开发一个Android应用程序，以在一个片段中显示地图。当我运行应用程序时，我总是会时不时地在日志中得到这个错误消息poppin。
Things I've tried:
我试过的东西:
- Erasing the debug.keystore and rebuilding the app.
- 擦除调试。密钥存储库和重建应用程序。
- Downgrading the Google Play Service and upgrading it again.
- 降级谷歌游戏服务并重新升级。
- Deselect Offline Work
- 取消选择离线工作
Nothing does the trick so far...
到目前为止，还没有什么办法。
Once upon the time in the Log tab :
在登录标签页上的时间:
2364-3928/com.example.android.app E/DynamiteModule: Failed to load module descriptor class: Didn't find class "com.google.android.gms.dynamite.descriptors.com.google.android.gms.googlecertificates.ModuleDescriptor" on path: DexPathList[[zip file "/data/app/com.example.android.app-2/base.apk"],nativeLibraryDirectories=[/data/app/com.example.android.app-2/lib/arm, /data/app/com.example.android.app-2/base.apk!/lib/armeabi-v7a, /vendor/lib, /system/lib]]
2364-3928/com.example.android.app I/DynamiteModule: Considering local module com.google.android.gms.googlecertificates:0 and remote module com.google.android.gms.googlecertificates:1
2364-3928/com.example.android.app I/DynamiteModule: Selected remote version of com.google.android.gms.googlecertificates, version >= 1
2364-3928/com.example.android.app W/System: ClassLoader referenced unknown path: /data/user/0/com.google.android.gms/app_chimera/m/00000000/n/armeabi
2364-3928/com.example.android.app D/ChimeraFileApk: Primary ABI of requesting process is armeabi-v7a
2364-3928/com.example.android.app D/ChimeraFileApk: Classloading successful. Optimized code found.
2364-3928/com.example.android.app D/GoogleCertificates: com.google.android.gms.googlecertificates module is loaded
2364-3928/com.example.android.app D/GoogleCertificatesImpl: Fetched 154 Google release certificates
1921-2130/? V/GoogleSignatureVerifier: com.example.android.app signature not valid. Found:
MIIB3TCCAUYCAQEwDQYJKoZIhvcNAQEFBQAwNzEWMBQGA1UEAwwNQW5kcm9pZCBEZWJ1ZzEQMA4G
A1UECgwHQW5kcm9pZDELMAkGA1UEBhMCVVMwHhcNMTYwNTE3MTYxNzM0WhcNNDYwNTEwMTYxNzM0
WjA3MRYwFAYDVQQDDA1BbmRyb2lkIERlYnVnMRAwDgYDVQQKDAdBbmRyb2lkMQswCQYDVQQGEwJV
UzCBnzANBgkqhkiG9w0BAQEFAAOBjQAwgYkCgYEAkafVu0j1zuB6+cpo6q5OsfhrlEFzVknFNs0c
vJorrlTTPZK3WSmkX9jZ0cp6oL60+4mHPouAR7Hq72gAs8u9Zh3eVrnV7uP7Rv2/z84DJuo34z1g
lahfkNPR/mCsYkK+ZqkC6uR46NnoftoKC/9vJSlUxYaBLT+mWvApz4rUKuMCAwEAATANBgkqhkiG
9w0BAQUFAAOBgQAERId+C7AD5Ew4Jv4mTmaZWBUtkinCKFSF4RtVa3xnHjL5xDPbAEq829gt+yx7
FkftGZO1x5nWEdAWyxiZgET3sKyl4ejRu1V5qvTMOcPMaVHw/e5v97FK8q756tQBcAu+Zs77P6MW
RxXtAwqeIkV1+L1rY8WueawfQ7Wbm1bPOg==
1921-2130/? V/GoogleSignatureVerifier: com.example.android.app signature not valid. Found:
MIIB3TCCAUYCAQEwDQYJKoZIhvcNAQEFBQAwNzEWMBQGA1UEAwwNQW5kcm9pZCBEZWJ1ZzEQMA4G
A1UECgwHQW5kcm9pZDELMAkGA1UEBhMCVVMwHhcNMTYwNTE3MTYxNzM0WhcNNDYwNTEwMTYxNzM0
WjA3MRYwFAYDVQQDDA1BbmRyb2lkIERlYnVnMRAwDgYDVQQKDAdBbmRyb2lkMQswCQYDVQQGEwJV
UzCBnzANBgkqhkiG9w0BAQEFAAOBjQAwgYkCgYEAkafVu0j1zuB6+cpo6q5OsfhrlEFzVknFNs0c
vJorrlTTPZK3WSmkX9jZ0cp6oL60+4mHPouAR7Hq72gAs8u9Zh3eVrnV7uP7Rv2/z84DJuo34z1g
lahfkNPR/mCsYkK+ZqkC6uR46NnoftoKC/9vJSlUxYaBLT+mWvApz4rUKuMCAwEAATANBgkqhkiG
9w0BAQUFAAOBgQAERId+C7AD5Ew4Jv4mTmaZWBUtkinCKFSF4RtVa3xnHjL5xDPbAEq829gt+yx7
FkftGZO1x5nWEdAWyxiZgET3sKyl4ejRu1V5qvTMOcPMaVHw/e5v97FK8q756tQBcAu+Zs77P6MW
RxXtAwqeIkV1+L1rY8WueawfQ7Wbm1bPOg==
1921-2130/? V/GoogleSignatureVerifier: com.example.android.app signature not valid. Found:
MIIB3TCCAUYCAQEwDQYJKoZIhvcNAQEFBQAwNzEWMBQGA1UEAwwNQW5kcm9pZCBEZWJ1ZzEQMA4G
A1UECgwHQW5kcm9pZDELMAkGA1UEBhMCVVMwHhcNMTYwNTE3MTYxNzM0WhcNNDYwNTEwMTYxNzM0
WjA3MRYwFAYDVQQDDA1BbmRyb2lkIERlYnVnMRAwDgYDVQQKDAdBbmRyb2lkMQswCQYDVQQGEwJV
UzCBnzANBgkqhkiG9w0BAQEFAAOBjQAwgYkCgYEAkafVu0j1zuB6+cpo6q5OsfhrlEFzVknFNs0c
vJorrlTTPZK3WSmkX9jZ0cp6oL60+4mHPouAR7Hq72gAs8u9Zh3eVrnV7uP7Rv2/z84DJuo34z1g
lahfkNPR/mCsYkK+ZqkC6uR46NnoftoKC/9vJSlUxYaBLT+mWvApz4rUKuMCAwEAATANBgkqhkiG
9w0BAQUFAAOBgQAERId+C7AD5Ew4Jv4mTmaZWBUtkinCKFSF4RtVa3xnHjL5xDPbAEq829gt+yx7
FkftGZO1x5nWEdAWyxiZgET3sKyl4ejRu1V5qvTMOcPMaVHw/e5v97FK8q756tQBcAu+Zs77P6MW
RxXtAwqeIkV1+L1rY8WueawfQ7Wbm1bPOg==
1921-2130/? V/GoogleSignatureVerifier: com.example.android.app signature not valid. Found:
MIIB3TCCAUYCAQEwDQYJKoZIhvcNAQEFBQAwNzEWMBQGA1UEAwwNQW5kcm9pZCBEZWJ1ZzEQMA4G
A1UECgwHQW5kcm9pZDELMAkGA1UEBhMCVVMwHhcNMTYwNTE3MTYxNzM0WhcNNDYwNTEwMTYxNzM0
WjA3MRYwFAYDVQQDDA1BbmRyb2lkIERlYnVnMRAwDgYDVQQKDAdBbmRyb2lkMQswCQYDVQQGEwJV
UzCBnzANBgkqhkiG9w0BAQEFAAOBjQAwgYkCgYEAkafVu0j1zuB6+cpo6q5OsfhrlEFzVknFNs0c
vJorrlTTPZK3WSmkX9jZ0cp6oL60+4mHPouAR7Hq72gAs8u9Zh3eVrnV7uP7Rv2/z84DJuo34z1g
lahfkNPR/mCsYkK+ZqkC6uR46NnoftoKC/9vJSlUxYaBLT+mWvApz4rUKuMCAwEAATANBgkqhkiG
9w0BAQUFAAOBgQAERId+C7AD5Ew4Jv4mTmaZWBUtkinCKFSF4RtVa3xnHjL5xDPbAEq829gt+yx7
FkftGZO1x5nWEdAWyxiZgET3sKyl4ejRu1V5qvTMOcPMaVHw/e5v97FK8q756tQBcAu+Zs77P6MW
UPDATE
I'm still having the error message, does anyone fix it since then?
我仍然有错误信息，从那以后有人修复吗?
/com.example.android.greenLeaf V/GoogleSignatureVerifier: com.google.android.gms signature not valid. Found:
MIIEQzCCAyugAwIBAgIJAMLgh0ZkSjCNMA0GCSqGSIb3DQEBBAUAMHQxCzAJBgNVBAYTAlVTMRMw
EQYDVQQIEwpDYWxpZm9ybmlhMRYwFAYDVQQHEw1Nb3VudGFpbiBWaWV3MRQwEgYDVQQKEwtHb29n
bGUgSW5jLjEQMA4GA1UECxMHQW5kcm9pZDEQMA4GA1UEAxMHQW5kcm9pZDAeFw0wODA4MjEyMzEz
MzRaFw0zNjAxMDcyMzEzMzRaMHQxCzAJBgNVBAYTAlVTMRMwEQYDVQQIEwpDYWxpZm9ybmlhMRYw
FAYDVQQHEw1Nb3VudGFpbiBWaWV3MRQwEgYDVQQKEwtHb29nbGUgSW5jLjEQMA4GA1UECxMHQW5k
cm9pZDEQMA4GA1UEAxMHQW5kcm9pZDCCASAwDQYJKoZIhvcNAQEBBQADggENADCCAQgCggEBAKtW
LgDYO6IIrgqWbxJOKdoR8qtW0I9Y4sypEwPpt1TTcvZApxsdyxMJZ2JORland2qSGT2y5b+3JKke
dxiLDmpHpDsz2WCbdxgxRczfey5YZnTJ4VZbH0xqWVW/8lGmPav5xVwnIiJS6HXk+BVKZF+JcWjA
sb/GEuq/eFdpuzSqeYTcfi6idkyugwfYwXFU1+5fZKUaRKYCwkkFQVfcAs1fXA5V+++FGfvjJ/Cx
URaSxaBvGdGDhfXE28LWuT9ozCl5xw4Yq5OGazvV24mZVSoOO0yZ31j7kYvtwYK6NeADwbSxDdJE
qO4k//0zOHKrUiGYXtqw/A0LFFtqoZKFjnkCAQOjgdkwgdYwHQYDVR0OBBYEFMd9jMIhF1Ylmn/T
gt9r45jk14alMIGmBgNVHSMEgZ4wgZuAFMd9jMIhF1Ylmn/Tgt9r45jk14aloXikdjB0MQswCQYD
VQQGEwJVUzETMBEGA1UECBMKQ2FsaWZvcm5pYTEWMBQGA1UEBxMNTW91bnRhaW4gVmlldzEUMBIG
A1UEChMLR29vZ2xlIEluYy4xEDAOBgNVBAsTB0FuZHJvaWQxEDAOBgNVBAMTB0FuZHJvaWSCCQDC
4IdGZEowjTAMBgNVHRMEBTADAQH/MA0GCSqGSIb3DQEBBAUAA4IBAQBt0lLO74UwLDYKqs6Tm8/y
zKkEu116FmH4rkaymUIE0P9KaMftGlMexFlaYjzmB2OxZyl6euNXEsQH8gjwyxCUKRJNexBiGcCE
yj6z+a1fuHHvkiaai+KL8W1EyNmgjmyy8AW7P+LLlkR+ho5zEHatRbM/YAnqGcFh5iZBqpknHf1S
KMXFh4dd239FJ1jWYfbMDMy3NS5CTMQ2XFI1MvcyUTdZPErjQfTbQe3aDQsQcafEQPD+nqActifK
Z0Np0IS9L9kR/wbNvyz6ENwPiTrjV2KRkEjH78ZMcUQXg0L3BYHJ3lc69Vs5Ddf9uUGGMYldX3Wf
MBEmh/9iFBDAaTCK
8 个解决方案
#1
14
When You make signed apk then you have to put SHA-1 Of that keystore in Google Api console where u enabled GoogleAPI V_2 enabled.Then Generate API key again and put that API key into your manifest file.
当你签署apk时，你必须在谷歌的Api控制台输入SHA-1，启用GoogleAPI V_2。然后再次生成API密钥，并将该API密钥放入您的清单文件中。
#2
13
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...
所以它应该被忽略直到未来更新…
#3
6
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.
通过检查其他遇到同样问题的人的互联网，将谷歌游戏服务更新到9.0.83。我在这里发现了一个关于如何解决这个问题的讨论。如果它能帮到你，你可以试着检查一下。
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.
一些解决方案是通过检查是否启用了离线工作，如果选中了脱机工作。然后，确认您是否有在项目级别构建中提到的谷歌服务的最新版本。gradle:类路径com.google.gms:谷歌服务:魅惑。在gradle同步完成后，清理并构建项目。
Try to update the SHA1 key in your project on Google Developer Console and update the Maps API key in your android project.
在您的项目中，尝试更新项目中的SHA1键，并在您的android项目中更新地图API键。
Also, some people fixed it by just deleting the debug.keystore file found in the android folder.
另外，一些人通过删除调试来修复它。在android文件夹中找到的密钥存储文件。
#4
5
As per Ian Barber's comment in this answer Google Play services version 10.0.1 will fix this issue.
根据伊恩·巴伯的评论，谷歌游戏服务版本10.0.1将解决这个问题。
Updgrade to the latest version (10.0.1 last time I looked), should go away.
升级到最新版本(上次我看了10.0.1)，应该消失。
Hope this will help you.
希望这对你有帮助。
Happy coading!!!
coading快乐! ! !
#5
5
Add this in project level gradle file:
将此添加到project level gradle文件中:
classpath 'com.google.gms:google-services:2.1.0'
类路径com.google.gms:谷歌服务:2.1.0的
and this one for module level gradle file:
这是模块级的文件:
compile 'com.google.android.gms:play-services:8.4.0'
编译的com.google.android.gms:游戏服务:8.4.0
and move below plugin at the end of file (at last line) of module level gradle file:
在模块级别的文件的末尾(最后一行)下方的插件下面移动:
apply plugin: 'com.google.gms.google-services'
应用插件:“com.google.gms.google-services”
#6
3
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.
我已经通过删除调试来修复它。在.android文件夹中找到的密钥存储文件。它将自动生成并使用该文件创建新的SHA1。
#7
3
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
Gnah。这让我烦了好几个小时!只需卸载谷歌Playservice的更新9.0.83。版本8.7.02在这里工作。同时也要记住:https://plus.google.com/+ChristopheBeyls/posts/LC2XCSoaVBJ。
#8
2
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.
您应该将Map api v2更改为v3:- Map api v3 coz的谷歌映射JavaScript api不再可用。本指南旨在帮助那些已经在使用谷歌映射JavaScript API v2的开发人员将他们的代码迁移到版本3。
#1
14
When You make signed apk then you have to put SHA-1 Of that keystore in Google Api console where u enabled GoogleAPI V_2 enabled.Then Generate API key again and put that API key into your manifest file.
当你签署apk时，你必须在谷歌的Api控制台输入SHA-1，启用GoogleAPI V_2。然后再次生成API密钥，并将该API密钥放入您的清单文件中。
#2
13
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...
所以它应该被忽略直到未来更新…
#3
6
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.
通过检查其他遇到同样问题的人的互联网，将谷歌游戏服务更新到9.0.83。我在这里发现了一个关于如何解决这个问题的讨论。如果它能帮到你，你可以试着检查一下。
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.
一些解决方案是通过检查是否启用了离线工作，如果选中了脱机工作。然后，确认您是否有在项目级别构建中提到的谷歌服务的最新版本。gradle:类路径com.google.gms:谷歌服务:魅惑。在gradle同步完成后，清理并构建项目。
Try to update the SHA1 key in your project on Google Developer Console and update the Maps API key in your android project.
在您的项目中，尝试更新项目中的SHA1键，并在您的android项目中更新地图API键。
Also, some people fixed it by just deleting the debug.keystore file found in the android folder.
另外，一些人通过删除调试来修复它。在android文件夹中找到的密钥存储文件。
#4
5
As per Ian Barber's comment in this answer Google Play services version 10.0.1 will fix this issue.
根据伊恩·巴伯的评论，谷歌游戏服务版本10.0.1将解决这个问题。
Updgrade to the latest version (10.0.1 last time I looked), should go away.
升级到最新版本(上次我看了10.0.1)，应该消失。
Hope this will help you.
希望这对你有帮助。
Happy coading!!!
coading快乐! ! !
#5
5
Add this in project level gradle file:
将此添加到project level gradle文件中:
classpath 'com.google.gms:google-services:2.1.0'
类路径com.google.gms:谷歌服务:2.1.0的
and this one for module level gradle file:
这是模块级的文件:
compile 'com.google.android.gms:play-services:8.4.0'
编译的com.google.android.gms:游戏服务:8.4.0
and move below plugin at the end of file (at last line) of module level gradle file:
在模块级别的文件的末尾(最后一行)下方的插件下面移动:
apply plugin: 'com.google.gms.google-services'
应用插件:“com.google.gms.google-services”
#6
3
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.
我已经通过删除调试来修复它。在.android文件夹中找到的密钥存储文件。它将自动生成并使用该文件创建新的SHA1。
#7
3
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
Gnah。这让我烦了好几个小时!只需卸载谷歌Playservice的更新9.0.83。版本8.7.02在这里工作。同时也要记住:https://plus.google.com/+ChristopheBeyls/posts/LC2XCSoaVBJ。
#8
2
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.
您应该将Map api v2更改为v3:- Map api v3 coz的谷歌映射JavaScript api不再可用。本指南旨在帮助那些已经在使用谷歌映射JavaScript API v2的开发人员将他们的代码迁移到版本3。