Description
When building to a Windows 10 Mobile device the app no longer open automatically as it did when building for 8.1, we should therefore inform the user of the need to open the app themselves similar to iOS
Steps to reproduce
1. Build to a Windows 10 mobile device using
appc run -p windows -T wp-device -S 10.0
Actual result
The following will be logged, the user will not be informed of the need to open the app themselves
[INFO] Finished building the application in 1m 8s 283ms
[INFO] Finished building the application in 1m 9s 870ms
[INFO] Installing and launching the application
[INFO] Project built successfully in 1m 11s 72ms
**User opens app**
[INFO] Finished launching the application
[INFO] Waiting for app to connect to log relay
Expected result
We should inform the user of the need to open the app on the device, similar to iOS
PR: https://github.com/appcelerator/windowslib/pull/39
Did we apply this changes to
titanium_mobile
? I guess not.The fix Gary made wasn't actually enough. It avoids the failure when we try to connect to win 10 mobile devices, but doesn't make any mention in the CLI telling the user to open the app, nor does it prevent failure when the command is "launch" and not "connect". I believe this PR addresses the issue: https://github.com/appcelerator/titanium_mobile_windows/pull/646
Verified as fixed, Now get an appropriate warning message returned in the event that the app cannot be launched automatically for windows 10 mobile:
Tested on: Windows 10 Pro Windows Phone 10.0 (Microsoft Lumia 640 LTE) Ti SDK: 5.3.0.v20160428072113 Appc NPM: 4.2.5-3 Appc Core: 5.3.0-40 Node: v4.4.2 *Closing Ticket.*