[TIMOB-20566] Windows: Building to a Windows 10 mobile device errors with 'Failed to conect to emulator'
| GitHub Issue | n/a |
|---|---|
| Type | Bug |
| Priority | Critical |
| Status | Closed |
| Resolution | Fixed |
| Resolution Date | 2016-03-16T23:32:27.000+0000 |
| Affected Version/s | Release 5.3.0 |
| Fix Version/s | Release 5.3.0, windowslib 0.4.4 |
| Components | Windows |
| Labels | qe-5.3.0 |
| Reporter | Ewan Harris |
| Assignee | Gary Mathews |
| Created | 2016-03-14T21:35:17.000+0000 |
| Updated | 2016-03-22T00:46:08.000+0000 |
Description
Description
When building to a Windows 10 mobile device the build errors out with the following[ERROR] Failed to conect to emulator. Full logs are attached as logs.txt.
When running both the test-device and test-wptool suites in windowslib the tests pass with no errors.
Steps to reproduce
1. Build a project to a Windows Mobile 10 device usingappc run -p windows -T wp-device -S 10.0
Actual result
The project will error out with[ERROR] Failed to conect to emulator
Expected result
The build should not fail and the app should be deployed to the deviceAttachments
| File | Date | Size |
|---|---|---|
| logs.txt | 2016-03-14T21:31:40.000+0000 | 298615 |
[~eharris] Was this due to the outdated windowslib on titanium_mobile 5_3_X? Or is this still occurring?
titanium_mobile_windows: https://github.com/appcelerator/titanium_mobile_windows/pull/584 windowslib: https://github.com/appcelerator/windowslib/pull/34
Verified using: Windows 10 Pro Appc NPM: 4.2.4-2 Appc Core: 5.2.1-17 Titanium SDK: 5.3.0.v20160318230005 Building to a Windows 10 Mobile device no longer errors out and the app is installed successfully. Created TIMOB-20611 to add logging to inform a user to open the app manually. Closing ticket