[TIMOB-18958] Windows: CLI builds hang on first try due to Powershell permission check in windowslib
| GitHub Issue | n/a |
|---|---|
| Type | Bug |
| Priority | Critical |
| Status | Closed |
| Resolution | Fixed |
| Resolution Date | 2015-06-25T16:57:16.000+0000 |
| Affected Version/s | n/a |
| Fix Version/s | Release 4.1.0 |
| Components | Tooling, Windows |
| Labels | n/a |
| Reporter | Christopher Williams |
| Assignee | Christopher Williams |
| Created | 2015-05-28T19:20:44.000+0000 |
| Updated | 2015-07-13T19:15:56.000+0000 |
Description
This is a bug in windowslib itself, specifically around https://github.com/appcelerator/windowslib/blob/dc9db61dbfa640460a933a738612d9a190e268b0/lib/env.js#L90
For me, when I just try to run a ti build, this eventually will cause windowslib to try and gathe renv info. The CMD prompt name will become "Windows PowerShell" and show no new output, effectively hung. I need to stop it with Ctrl+C and then open Powershell prompt as an administrator and give more expansive scripting rights to the system. This value _does not seem to persist across reboots for me_.
https://github.com/appcelerator/windowslib/pull/17
https://github.com/appcelerator/titanium_mobile/pull/6903
Verified using: Windows 8.1 Appc CLI (NPM): 4.1.0 Appc CLI (Registry): 4.1.0 Ti SDK: 4.1.0.GA When building using the various PowerShell permissions there are no issues Closing ticket