[TIMOB-17251] CLI: Passing wrong password and correct alias, when building for android, results in Error for both
| GitHub Issue | n/a |
|---|---|
| Type | Improvement |
| Priority | Low |
| Status | Open |
| Resolution | Unresolved |
| Affected Version/s | Release 3.3.0 |
| Fix Version/s | n/a |
| Components | Android, CLI |
| Labels | cb-tooling, qe-3.3.0 |
| Reporter | Olga Romero |
| Assignee | Chris Barber |
| Created | 2014-06-30T22:10:22.000+0000 |
| Updated | 2017-01-04T17:02:42.000+0000 |
Description
To reproduce
1. Create a default project via Studio 2. Distribute - Android App Store 3. Type a wrong password, entering credentialsActual result
[ERROR] : Invalid "--store-password" value "hhhhhhhhhhhh"
For help, run: titanium help build
[ERROR] : Invalid "--alias" value "correct value here"
FYI, I cannot validate the alias until the store password works. I probably should not be trying to validate the alias if the password is bad. -The fix is probably trivial.-
UPDATE 1/4/2017
Turns out this is NOT trivial to fix. The problem is when\-\-no\-promptis specified, the Titanium CLI will validate ALL command line options and in order to validate\-\-alias, we need to have a valid store password. To fix this, we need a way of\-\-aliasto know whether or not\-\-store-passwordwas valid. We can hack a flag in the Android build that tracks this, but this is not ideal. It would be better if the Titanium CLI could track this for us, but this again is not trivial.