Android build

Keystore was tampered with, or password was incorrect

The upload keystore can’t be read

Keystore was tampered with, or password was incorrect. Release builds are signed with your upload keystore, and Gradle couldn’t open it: wrong path, wrong password or wrong key alias.

Updated

What this error means

Release builds are signed with your upload keystore, and Gradle couldn’t open it: wrong path, wrong password or wrong key alias.

Why it happens

The release signing config points at an upload keystore Gradle could not open. The path is wrong, or the store password, key alias, or key password does not match.

The message tools print

com.android.ide.common.signing.KeytoolException: Failed to read key upload from store "/home/runner/work/harbor/harbor/android/app/release.keystore": Keystore was tampered with, or password was incorrect

How to fix it

  1. Check the keystore path, store password, key alias and key password of the release signing config.
  2. If they come from CI secrets, make sure the secret decodes to the same keystore file.
  3. Never create a new keystore for an app already on Google Play — Play only accepts the original upload key.

Check a log that shows this

Paste the failing step into the build error explainer. It matches this message, and any others in the same log, in your browser. Nothing is uploaded.

Other Android build errors

Let the Android build run in CI

CapWrapp builds the release on GitHub Actions with the JDK and Android SDK the project needs, and signs it with the upload keystore it stores for you.

  • Free to start
  • No credit card
  • Sign in with Google or GitHub