在 Eclipse 中运行我的签名发布密钥库时出现问题

发布于 2024-10-04 06:45:43 字数 296 浏览 0 评论 0原文

我无法在 Eclipse 中运行已签名的发布密钥库:

我收到错误:

Keystore was tampered with, or password was incorrect

如何解决此问题?

这是错误: alt text

这是我成功签署密钥库的情况: 替代文本

I am unable to run my signed, release keystore in Eclipse:

I get the error:

Keystore was tampered with, or password was incorrect

How can I resolve this?

Here is the error:
alt text

Here is me successfully signing the keystore:
alt text

如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。

扫码二维码加入Web技术交流群

发布评论

需要 登录 才能够评论, 你可以免费 注册 一个本站的账号。

评论(5

千秋岁 2024-10-11 06:45:43

在 Windows->Preferences->Android->Build 中,您只需更改 DEBUG KEYSTORE 即可。您在此处指定的密钥库不是用于签署要发布的应用程序,而只是用于调试。

与默认调试密钥库一样,自定义调试密钥库需要具有以下内容:

Keystore password: "android"
Key alias: "androiddebugkey"
Key password: "android"

除了密钥库本身的名称、有关组织单位的信息以及别名后面的密钥之外,所有数据都必须与 默认调试密钥库

In Windows->Preferences->Android->Build you can just change your DEBUG KEYSTORE. The Keystore you specify there, is not for signing an app for release, but just for debugging.

Like the default debug keystore, the custom debug keystore needs to have the following:

Keystore password: "android"
Key alias: "androiddebugkey"
Key password: "android"

Except for the name of the keystore itself, information about the organizational units and the key behind the alias, all data have to be same as the default debug keystore

最终幸福 2024-10-11 06:45:43

我可以建议的一个明显的事情是检查密码是否适合适当的语言和大小写,并确保您的密钥库处于一致的状态(但如果您没有生成校验和,则不知道如何做到这一点)。

对于密钥库的一般建议:始终进行备份。

此外,密钥库可以确保您是在更新应用程序时创建该应用程序的人。 IOW,它是一个只允许您更新应用程序的工具。

The obly thing i can advise is to check the password for the appropriate language and case, and also make sure your keystore is in consistent state(but don't have a clue how to do it, if you haven't generated checksum).

The general advise for keystores: always make a backup.

Also, keystore is the thing to make sure you're one who have created the application in the moment of updating it. IOW, it is a tool to let only you update your application.

我一向站在原地 2024-10-11 06:45:43

希恩,
我支持弗拉基米尔备份密钥库的建议。

为了避免出现密钥库错误,只需备份当前密钥库和密钥库即可。然后删除它(从/home/user/.android/debug.keystore)&重新编译应用程序并eclipse 会自动为您生成一个密钥库。

始终备份您的密钥库以发布/重新发布应用程序。

祝你好运!

Sheehan ,
I support Vladimir's suggestion to backup your keystores.

To avoid getting keystore errors Simply backup the current keystore & then delete it(from /home/user/.android/debug.keystore) & recompile the app & eclipse will automatically generate a keystore for you.

Always do backup your keystores for publishing/republishing the app.

Good Luck!

尴尬癌患者 2024-10-11 06:45:43

最简单的方法是在 eclipse 本身内部创建密钥库,作为导出过程的一部分。导出应用程序时,单击生成新密钥库的选项。填写适当的信息,Eclipse 将为您生成一个新的有效密钥库。

并始终备份您的密钥库。我有一个 USB 驱动器,里面有我所有密钥库的副本。

The easiest way is to create a keystore is from inside eclipse itself as part of the export process. When excporting your app click the option to generate a new keystore. Fill out the appropriate information and Eclipse will generate a new, valid keystore for you.

And always backup your keystores. I have a usb drive that has a copy of all of my keystores.

紫瑟鸿黎 2024-10-11 06:45:43

我对你想在这里实现的目标感到困惑。是不是不能按原样编辑?当准备将其交付到市场时,您将在未签名的情况下导出它(即没有调试密钥库)。

有可能是您选中了“外部 jar 时强制错误...”选项吗?

我第三(或第四)其他人在这里所说的关于备份和删除 ~/.android 密钥库的内容 -
http://developer.android.com/guide/appendix/faq/troubleshooting .html#signingcalendar

假设您已经这样做了,我不会“为您搜索”,但这可能是一个日食问题。

希望你能尽快开始。

I am confused about what you are trying to achieve here. Is it that you just can't edit it as it is? When preparing it for delivery to the market, you would be exporting it unsigned (ie without the debug keystore).

Could it possibly be that you have the "force error when external jars..." option checked?

I third (or fourth) what others have said here about backing up and deleting the keystore at ~/.android -
http://developer.android.com/guide/appendix/faq/troubleshooting.html#signingcalendar.

Assuming that you've already done so, I won't "google that for you", but it might be an eclipse problem.

Hope you get it going soon.

~没有更多了~
我们使用 Cookies 和其他技术来定制您的体验包括您的登录状态等。通过阅读我们的 隐私政策 了解更多相关信息。 单击 接受 或继续使用网站,即表示您同意使用 Cookies 和您的相关数据。
原文