我有一个密钥库（.jks），我用来签署用于Google Play的应用程序（.APK）的上一版。那是一年前左右。
现在，当我尝试构建和使用密钥库时，Android Studio给我以下错误错误：
无法构建签名的APK。钥匙店被篡改，或密码不正确。
Android Studio version information:
Android Studio Bumblebee | 2021.1.1 Patch 3
Build #AI-211.7628.21.2111.8309675, built on March 16, 2022
Runtime version: 11.0.11+0-b60-7590822 amd64
VM: OpenJDK 64-Bit Server VM by JetBrains s.r.o.
Linux 5.11.0-49-generic
GC: G1 Young Generation, G1 Old Generation
Memory: 2048M
Cores: 12
Registry: external.system.auto.import.disabled=true
Non-Bundled Plugins: org.jetbrains.kotlin (211-1.6.21-release-334-AS7442.40)
Current Desktop: ubuntu:GNOME
这是我试图运行的功能：
build =＆gt;生成签名的捆绑包 / apk
显示以下屏幕...
当我单击[完成]按钮时，Android Studio尝试构建＆amp;它因错误而失败：
无法构建签名的APK。密钥店被篡改，或密码不正确。
这是一个不正确的错误
，这是不正确的，因为我使用密码管理器存储密码，所以我知道我有正确的密码。我还保留了上次运行此功能的屏幕截图，以便可以确认关键别名，并且也是正确的。
我尝试的事情
- 我尝试重建几次＆amp;有错误。
- 我关闭＆amp;重新启动Android Studio＆amp;仍然有错误。
在某一时刻，Android Studio坠毁了Bug Report＆amp;我再次尝试了＆amp;它再次失败。
为什么发生此错误？
我发现了其他一些人报告包含特殊字符（@！等）的密码似乎是一个问题=“ nofollow noreferrer”>在此链接上。
它似乎确实是相同的失败，但我终于使它起作用＆amp;我会发布答案。
其他信息 - Android Studio 09/2023
现在，我正在运行最新版本的Android Studio，并在1年零4个月后发布此更新，因为我仍然看到Android Studio告诉我我的密码的问题是不正确的 - 甚至认为不是。
请记住我的密码来自密码管理器，我将其粘贴到 - 没有打字错误或密码错误。
分辨率
每当我尝试构建签名的APK并收到错误时，我只需重新启动Android Studio并再次构建签名的APK，粘贴在相同的密码中，然后成功。
Android Studio版本信息
Android Studio Giraffe | 2022.3.1 Patch 1
Build #AI-223.8836.35.2231.10671973, built on August 17, 2023
Runtime version: 17.0.6+0-17.0.6b829.9-10027231 amd64
VM: OpenJDK 64-Bit Server VM by JetBrains s.r.o.
Linux 6.2.0-32-generic
GC: G1 Young Generation, G1 Old Generation
Memory: 2048M
Cores: 12
Registry:
external.system.auto.import.disabled=true
ide.text.editor.with.preview.show.floating.toolbar=false
当前桌面：ubuntu：gnome
I have a Keystore (.jks) which I used to sign the previous release of my App (.APK) for Google Play. That was 1 year ago or so.
Now, when I attempt to build and use my keystore, Android Studio gives me the following incorrect error:
Could not build signed APK. Keystore was tampered with, or password was incorrect.
Android Studio version information:
Android Studio Bumblebee | 2021.1.1 Patch 3
Build #AI-211.7628.21.2111.8309675, built on March 16, 2022
Runtime version: 11.0.11+0-b60-7590822 amd64
VM: OpenJDK 64-Bit Server VM by JetBrains s.r.o.
Linux 5.11.0-49-generic
GC: G1 Young Generation, G1 Old Generation
Memory: 2048M
Cores: 12
Registry: external.system.auto.import.disabled=true
Non-Bundled Plugins: org.jetbrains.kotlin (211-1.6.21-release-334-AS7442.40)
Current Desktop: ubuntu:GNOME
Here is the functionality I'm attempting to run:
Build => Generate Signed Bundle / APK
Displays the following screens...
When I click [Finish] button Android Studio attempts to build & it fails with the error:
Could not build signed APK. Keystore was tampered with, or password was incorrect.
That Is an Incorrect Error
However, that is not correct because I use a password manager to store the password, so I know I have the correct password. I also kept screenshots of the last time I ran this functionality so I could confirm the key alias and it is correct also.
Things I Tried
- I tried rebuilding a couple of times & got the error.
- I closed & restarted Android Studio & still got the error.
At one point Android Studio crashed with a bug report & I tried again & it failed again.
Why does this error occur?
I discovered some other people reporting what seemed to be an issue with having a password that contained special chars (@ !, etc) at this link.
It does seem to be the same failure, but I finally got it to work & I will post the answer.
Additional Information - Android Studio 09/2023
I'm now running the latest version of Android Studio and posting this update 1 year and 4 months later because I still see the problem where Android Studio tells me that my password is incorrect -- even thought it isn't.
Keep in mind my password for this comes from a password manager and I paste it in -- no typing mistakes or password mistakes.
The Resolution
Whenever I attempt to build a signed APK and I get the error, then I simply restart Android Studio and build the signed APK again, paste in the same password and it succeeds.
Android Studio Version Information
Android Studio Giraffe | 2022.3.1 Patch 1
Build #AI-223.8836.35.2231.10671973, built on August 17, 2023
Runtime version: 17.0.6+0-17.0.6b829.9-10027231 amd64
VM: OpenJDK 64-Bit Server VM by JetBrains s.r.o.
Linux 6.2.0-32-generic
GC: G1 Young Generation, G1 Old Generation
Memory: 2048M
Cores: 12
Registry:
external.system.auto.import.disabled=true
ide.text.editor.with.preview.show.floating.toolbar=false
Current Desktop: ubuntu:GNOME
发布评论
评论（3）
我有同样的问题。在我的情况下，它是
isDebuggable = truein Build.gradle（buildTypes）I have had same problem. In my case it was
isDebuggable = truein build.gradle (buildTypes)我启动了一个控制台窗口，并对我的密钥库进行了以下操作。
$ keytool -list-keystore'fakenmae.jks'-storepass fake-password-same-same-one-on-i-inded in android-studio我看到了在控制台中打印出的键盘的详细信息：
由于我必须提供密码，因此确认我确实使用了正确的密码。
它还确认了密钥库没有被篡改（损坏）。
此时我有点困惑。
<<<<<<<<<<<<<<<<<<<<<<< strong>
我再次尝试了AndroidStudio，并构建了签名的APK
。 的信息。
Android Studio很想听到某人知道为什么
I started a console window and ran the following against my keystore.
$ keytool -list -keystore 'fakeNmae.jks' -storepass fake-password-same-one-i-used-in-android-studioI saw the details of my keystore printed out in the console:
Since I had to supply my password this confirmed that I was indeed using the correct password.
It also confirms that the keystore was not tampered with (corrupted).
I was a bit confused at this point.
Solution
I started AndroidStudio again & tried it again and it built the signed APK with no problem. I was able to upload it to Google Play.
Very odd. It seems that listing the details somehow fixed the issue in Android Studio. Would love to hear something about this from someone who might know why.
Maybe it has to do with that new warning about the PKCS12 format??
就我而言，这是错误的别名，在创建密钥库期间指定别名，因此，如果别名与创建过程中指定的别名不同，则确定会出现错误。
In my case it was the wrong alias, alias is specified during the creation of the keystore, so if the alias is not the same as the one specified during creation you definite get an error.