安卓证书问题
如果我丢失了用keytool创建的原始certificate.keystore文件，但有准确的终端输出和我输入的所有内容，是否足以创建一个新的证书，android市场发布网站会接受而不用说新的apk必须使用相同的证书签名？
If I lost the original certificate.keystore file created with keytool, but have the exact terminal output and all the stuff I entered to make it, is that enough to be able to create a new certificate that the android market publish site will accept without saying that the new apk must be signed with the same certificate?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
这是谷歌安卓市场的一个主要缺陷。与苹果不同，您可以使用苹果开发者帐户请求证书，谷歌还没有这样的服务。如果您丢失了证书，就是这样。您将无法发布应用程序的更新版本以供人们下载。
最好的办法是让您的用户群知道该应用程序有新版本，其中的更改导致无法正常更新，他们需要卸载旧版本并下载新版本，从应用程序商店取消发布旧版本并发布新的。 （这有点善意的谎言，但人们不会哭太多，这比说你丢失了证书要好得多，大多数用户甚至不知道你在做什么）
然后保留你的证书副本以进行备份并保持安全！！！通过电子邮件将其发送给自己，将其放在未命名的闪存驱动器上（以防它被盗，人们不会知道证书的用途）。 Gmail 很好，因为它可以轻松地使用关键字检索几个月前的邮件。如果需要的话，可以将其刻录到 CD 上并将其放入药柜中。
希望这有帮助，祝你好运
This is a MAJOR flaw in the google android market. unlike apple where you can request your certificate with your apple developer account, google has no such service yet. If you loose your certificate, thats it. You will be unable to publish an updated version of your app for people to download.
Best thing to do is let your userbase know there is a new version of the app out with changes that made it impossible to update normally, and they need to uninstall the old version and download the new version, unpublish the old version from the app store and publish the new one. (its a bit of a white lie, but people wont cry too much, and its a lot better than saying you lost the certificate, most users wont even know what you are on about)
Then keep your certificate duplicated for backups and keep it SAFE!!! Email it to yourself, put it on a unnamed flashdrive (incase it gets stolen people wont know what the certificates for). Gmail is good because its easy to retrieve mail from months ago with keywords. Burn it on a CD and put it in your medicine cabinet if you have to.
Hope this helps, good luck
我认为生成的证书和私钥不会相同。
I dont think the generated certificate and the private key will be the same.