英文:
Signing an Android .apk from a 32 hex pair signing key
问题
我有一个Android应用程序，我接管了它的开发工作，现在我正在尝试向Google Play商店推送更新。原始开发者已经给了我签名密钥，但我不确定如何从这个签名密钥创建证书或密钥库。
我收到的密钥格式如下：
1B:96:51:EE...43（由冒号分隔的32个十六进制对值）
我熟悉如何从自签名证书创建密钥库，并使用该密钥库对.apk进行签名。但是，我不确定如何从给定的签名密钥实现这一点。
我已经阅读了Google提供的文档 Google App Signing，但我在这份文档中没有找到如何使用我收到的签名密钥格式的说明。
英文:
I have an android app that I have taken over development for and I am trying to push an update to the Google Play store. The original developer has given me the signing key, but I am not sure how to create a certificate or keystore from this signing key.
key format I was given:
1B:96:51:EE...43 (32 hex pair values separated by a colon)
I am familiar with creating a keystore from a self-signed certificate and using that keystore to sign the .apk. But, I am not sure how to achieve this from the given signing key.
I have read over the documentation provided by Google Google App Signing
I do not see in this documentation how to utilize the signing key in the format it was given to me.
答案1
得分: 1
使用这种格式，很不可能他给你的实际上是签名密钥。这更像是证书指纹，你无法使用它来签名APK。
你应该要求之前的开发者提供他们用来签名APK的密钥库文件。这应该是一个扩展名为jks、keystore或可能是p12的文件。
如果该应用程序已经在Play签名中注册，你也可以联系Play开发者支持，要求他们重置上传密钥（他们会提供给你操作指南）。
英文:
With this format, it is very unlikely that what he gave you is actually the signing key. This looks more like the certificate fingerprint, from which you would not be able to sign an APK.
You should request the previous developer to give you the keystore they were signing the APK with. This should be a file with the extension jks, keystore, or possibly p12.
If the app was enrolled in Play Signing, you could alternatively contact the Play Developer Support and ask them to reset the upload key (they will give you the instructions).
通过集体智慧和协作来改善编程学习和解决问题的方式。致力于成为全球开发者共同参与的知识库，让每个人都能够通过互相帮助和分享经验来进步。
评论