Add code signing for Android release artefacts #1268
Labels
android
The issue relates to Android mobile support.
enhancement
New features, or improvements to existing features.
What is the problem or limitation you are having?
Briefcase currently supports code signing on macOS and Windows. Code signing is also required for Android release artefacts.
Describe the solution you'd like
briefcase package android --identity <identity>
should accept a path to a keystore, and use that keystore to sign the app.briefcase package android
should prompt the user to do one of:*.jks
in the project folder, the.android
subfolder of the project folder, or the user's~/.android
folder, and provide those files as candidate keystores to use.org.example.myapp.jks
in a.android
folder of the project directory, and use that keystore.Describe alternatives you've considered
Continue to require manual signing. The process of generating a keystore and signing the app; this is a simplification process.
Additional context
No response
The text was updated successfully, but these errors were encountered: