-
-
Notifications
You must be signed in to change notification settings - Fork 366
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
KeytoolException: Failed to read key AndroidDebugKey from store: Invalid keystore format #1112
Comments
This is probably not a new problem, because Android Studio has come with Java 11 since 2021. We just haven't seen it before because most of our users are Android novices whose first Android build was through Briefcase, not Android Studio. |
i using command briefcase package android FAILURE: Build failed with an exception.
how solution |
and how to use own sdk root i get message like this ** WARNING: ANDROID_SDK_ROOT does not point to an Android SDK **
how to use own sdk root my .bashrc file is for examples#export JAVA_HOME=/usr/lib/jvm/java-17-openjdk-amd64/ #export ANDROID_HOME=/root/Android/Sdk #export PATH=$PATH:/opt/gradle/gradle-8.1.1/bin |
You can work around the "Invalid keystore format" error by deleting the debug.keystore file and then running The "doesn't appear to contain an Android SDK" error means that either the ANDROID_SDK_ROOT directory doesn't exist, or it doesn't contain an executable |
is it possible to build an Android briefcase with our own keystore like the
myown.keystore file
Pada tanggal Rab, 10 Mei 2023 04.08, Malcolm Smith ***@***.***>
menulis:
… You can work around the "Invalid keystore format" error by deleting the
debug.keystore file and then running briefcase again.
The "doesn't appear to contain an Android SDK" error means that either the
ANDROID_SDK_ROOT directory doesn't exist, or it doesn't contain an
executable cmdline-tools/latest/bin/sdkmanager.
—
Reply to this email directly, view it on GitHub
<#1112 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AMNJC24DEJAKKFMNK4QMMLTXFKW4LANCNFSM6AAAAAAVIWWF4U>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
I success build debug apk . but when i run it on my android . suddenly my android application exits itself
|
Briefcase doesn't currently have an option for this (#865 (comment)). You can do it by using Android Studio to open the build/.../android/gradle directory, and then running the command Build > Generate Signed Bundle / APK. |
Instead of installing the APK manually, try using |
FYI - I've opened #1268 so the feature request of signing Android apps isn't forgotten. |
Reported by warchants on Discord, with the following log:
The first time a debug build is done on any given machine, the Android Gradle plugin creates the debug.keystore file with a randomly-generated key, and then uses it for all subsequent debug builds of all apps on that machine. Unfortunately it looks like there's been a backward-incompatible change to the file's format, so files created by new Java versions (e.g. the version that comes with new versions of Android Studio) cannot be read by the Java version that Briefcase currently uses.
Based on this discussion, we could fix this by moving to Java 8u301 or newer. I've confirmed that it works OK with Corretto version 1.8.0_352.
Such a new version is not available at https://github.com/AdoptOpenJDK/openjdk8-binaries, which Briefcase currently uses. But its successor, https://adoptium.net/, currently offers version 8u362. See #1065.
The text was updated successfully, but these errors were encountered: