[TIMOB-20370] Windows: Running desktop app doesn't show logs in console
GitHub Issue | n/a |
---|---|
Type | Bug |
Priority | Critical |
Status | Closed |
Resolution | Fixed |
Resolution Date | 2016-02-11T15:39:18.000+0000 |
Affected Version/s | Release 5.2.0 |
Fix Version/s | Release 5.3.0, windowslib 0.4.0 |
Components | Windows |
Labels | n/a |
Reporter | Christopher Williams |
Assignee | Christopher Williams |
Created | 2016-02-08T16:30:47.000+0000 |
Updated | 2016-04-19T18:03:19.000+0000 |
Description
If you run a Windows 10 app on desktop
{-T ws-local}
it'll require some user input (Enter) to set up the first time. But after that, it goes automatically. In both cases, the CLi basically just exits after the app gets launched, and I see no logs from the app whatsoever.
Additionally, I've seen the first few times the app seemed to just close/crash without fully running (this was the mocha unit test app, didn't see any activity before app disappeared).
I _believe_ this is related to needing to do some black magic/voodoo like this: https://msdn.microsoft.com/en-us/library/windows/apps/hh780593.aspx If I debug NMocha manually under VS2015 it does connect to a logger socket and spit out the logs. If I run the app outside VS2015 though, it appears to never work, even if I enable loopbacks according to the docs I linked above. Apparently VS also does something else to make it work...
Finally used this tool: http://loopback.codeplex.com/ And that made it work! So now I have to see if we can ship some tool that can do pretty much the same thing with command lien args and not a GUI.
Verified using: Windows 10 Pro Visual Studio 2015 Community Update 2 Appc Core: 5.3.0-20 Appc NPM: 4.2.5-2 Ti SDK: 5.3.0.v20160418111755
When building a project for
ws-local
logs are now shown in the console, created TIMOB-23237 to deal with parity in Ti.API.log Closing ticket