Hi Team,
Looking for some opinions on the keystore password prompt, when building
for android.
TL;DR; is this feature worth keeping?
If you're not aware, if you leave either the store password or the key
password blank/empty string inside
the build.json file, then we have a gradle implementa
I think we should not be making our own password-based or other secure
build tools within the Cordova project unless it is absolutely necessary.
This looks like a problem that is not unique to Cordova app development.
I think this is something that should be done by other tools such as
Gradle, An
If we deprecate the password prompt feature and remove in the next
major, this leaves the user with the following options:
- Use build.json to have cordova sign apps for the user automatically.
- Not use build.json, which gives the user the unsigned apk, which
they'll have to sign themselves us
Nightly build #1476 for cordova has succeeded!
The latest nightly has been published and you can try it out with 'npm i -g
cordova@nightly'
For details check build console at
https://builds.apache.org/job/cordova-nightly/1476/consoleFull
-
Jenkins for Apache Cordova
---
My suggestion would be to remove the prompt, and insist that the value
either come from build.json
and/or if we are willing to do a little more work, it could come from an
env variable
SIGNING_PASSKEY=123123kasdj cordova build android --release
On Wed, Jul 15, 2020 at 7:08 PM Norman Breau wrote:
