在调试生成的证书SHA1指纹不匹配，我使用密钥库 [英] Cert SHA1 fingerprint generated at debug does not match with the keystore I'm using

问题描述

这是这个问题：当我运行我的应用程序是使用谷歌Play游戏服务我得到一个错误尝试在应用程序配置不正确签署检查包名称和证书签名匹配创建客户端ID开发者控制台。

This is the issue: When I run my app which is using Google Play Game Services I got an error trying to sign in "The application is incorrectly configured. Check that the package name and sign in certificate match the client ID created in Developer Console".

我检查的建议和一切看起来不错，但阅读的logcat我注意到SHA1指纹是不一样的我的.keystore文件。这是一个有点困惑，因为当我执行keytool命令来查看的.keystore文件的信息，我可以看到，与在开发者控制台我的应用程序ID有关的相同SHA1。

I checked the suggested and everything look OK, but reading the Logcat I noted the SHA1 fingerprint is not the same of my .keystore file. It's a little confused because when I execute the keytool command to view the .keystore file information, I can see the same SHA1 that is related with my app id in the Developer Console.

非常感谢你的帮助。

推荐答案

我发现这个问题。当您配置谷歌Play游戏服务，你有你的.keystore文件和同时您必须添加位于... /。Android的/，无论是指纹debug.keystore文件添加SHA1指纹在开发者控制台链接的应用程序的链接被添加。这是因为当我跑我的应用程序使用的.keystore文件没有在开发者控制台，其中采取了默认SHA1是发行配置。

I found the issue. When you configure Google Play Game Services, you have to add the SHA1 fingerprint of you .keystore file and ALSO you have to add the debug.keystore file located at .../.android/, both fingerprints are added at the linked application link in the Developer Console. It is because when I run my app the .keystore file used was not configured at Developer Console, where the default SHA1 taken is the release.

这篇关于在调试生成的证书SHA1指纹不匹配，我使用密钥库的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！