简体繁体 English

Google Play 应用签名证书和上传证书在 Google Play 控制台中创建了相同的 SHA1 密钥

[英]Both Google Play App Signing Certificate and Upload Certificate created Same SHA1 key in Google Play Console

原文 2019-05-29 06:57:21 8 1 android/ google-play/ sha1

Recently i opted Google Play console App Signing feature into my existing app using "Export and upload a key from a Java keystore" option in Release Management->App Signing.最近，我使用 Release Management->App Signing 中的“Export and upload a key from a Java keystore”选项在我现有的应用程序中选择了 Google Play 控制台应用程序签名功能。

I had followed the first 3 steps and uploaded the "App Signing Private key".我遵循了前 3 个步骤并上传了“应用签名私钥”。

After this step, I got the "App Signing Certificate " and "Upload Certificate" having the same SHA1 Fingerprint Certificate for both.在这一步之后，我获得了具有相同 SHA1 指纹证书的“应用签名证书”和“上传证书”。

Does anybody face this issue in Google Play console?有人在 Google Play 控制台中遇到过这个问题吗？ TIA TIA

1 个解决方案

The App Signing Certificate and Upload Certificate have same SHA1 when we tried to upload the keystore of an existing app in the play store.当我们尝试上传 Play 商店中现有应用的密钥库时，应用签名证书和上传证书具有相同的 SHA1。

Solution Which worked for me:(To change the SHA1 in Upload Certificate)对我有用的解决方案：（更改上传证书中的 SHA1）

-->Create a new keystore file using the exisitng keystore. --> 使用现有的密钥库创建一个新的密钥库文件。

-->Upload the new key into the "App Signing" section under keystore management. --> 将新密钥上传到密钥库管理下的“应用签名”部分。

It will take 24-48hrs to reflect the new SHA1 in Playstore console.在 Playstore 控制台中反映新的 SHA1 需要 24-48 小时。

*contact google play store customer support for more details regarding this. *请联系 google play 商店客户支持以获取有关此的更多详细信息。

*Note: If you are releasing test build through play store for testers, use the test SHA1 key(if app is having any google services which requires) which is completely different from the upload certificate in the console. *注意：如果您通过 Play 商店为测试人员发布测试版本，请使用与控制台中的上传证书完全不同的测试 SHA1 密钥（如果应用程序具有任何需要的谷歌服务）。