[TIMOB-19745] Windows: CLI can hang when encrypting files due to invalid jdkInfo object
GitHub Issue | n/a |
---|---|
Type | Bug |
Priority | Critical |
Status | Closed |
Resolution | Fixed |
Resolution Date | 2015-10-20T03:55:01.000+0000 |
Affected Version/s | n/a |
Fix Version/s | Release 5.1.0 |
Components | Windows |
Labels | n/a |
Reporter | Gary Mathews |
Assignee | Gary Mathews |
Created | 2015-10-19T23:59:00.000+0000 |
Updated | 2015-10-30T20:03:35.000+0000 |
Description
The CLI can hang if
jdkInfo
is null
during encryption.
This usually happens on the first build or re-builds when the encryptJS
flags gets set to true
after the validate
build command [\[1\]](https://github.com/appcelerator/titanium_mobile_windows/blob/master/cli/commands/_build/validate.js#L155).
The reason encryptJS
gets set to true
is due to buildVerify
[\[2\]](https://github.com/appcelerator/appc-cli-titanium/blob/master/hook/titanium.js#L207).
If buildVerify
is successful and we are online the encryptJS
flag will always be set to true
regardless of deploy type.
This is why Windows projects are always encrypted on first build or re-builds even if they are being deployed for development.
PR : https://github.com/appcelerator/titanium_mobile_windows/pull/454
Verified using: Windows 8.1 Appc Core: 5.1.0-41 Appc NPM: 4.2.1 Ti SDK: 5.1.0.v20151028190028 When building a newly created project for Windows emulator for the first time the encryption of files does no longer causes the CLI process to hang. Closing ticket