{ "id": "164135", "key": "TIMOB-24062", "fields": { "issuetype": { "id": "1", "description": "A problem which impairs or prevents the functions of the product.", "name": "Bug", "subtask": false }, "project": { "id": "10153", "key": "TIMOB", "name": "Titanium SDK/CLI", "projectCategory": { "id": "10100", "description": "Titanium and related SDKs used in application development", "name": "Client" } }, "fixVersions": [ { "id": "17608", "name": "Release 6.1.0", "archived": false, "released": true, "releaseDate": "2017-05-26" } ], "resolution": { "id": "11", "description": "Is not a bug in our product", "name": "Not Our Bug" }, "resolutiondate": "2016-11-16T00:54:01.000+0000", "created": "2016-10-21T14:08:45.000+0000", "priority": { "name": "High", "id": "2" }, "labels": [ "qe-6.0.0" ], "versions": [ { "id": "16980", "description": "New V8", "name": "Release 6.0.0", "archived": false, "released": true, "releaseDate": "2016-11-15" } ], "issuelinks": [], "assignee": { "name": "kiguchi", "key": "kota", "displayName": "Kota Iguchi", "active": false, "timeZone": "America/Los_Angeles" }, "updated": "2017-02-01T22:18:52.000+0000", "status": { "description": "The issue is considered finished, the resolution is correct. Issues which are closed can be reopened.", "name": "Closed", "id": "6", "statusCategory": { "id": 3, "key": "done", "colorName": "green", "name": "Done" } }, "components": [ { "id": "12642", "name": "Windows", "description": "Windows authoring support" } ], "description": "h5.Description\r\n\r\nWhen building to a Windows 10 Mobile emulator I am not receiving any logging, Windows Phone 8.1 emulators work fine. Not sure whether this issue in the Windows side of RN could be related https://github.com/ReactWindows/react-native-windows/issues/683\r\n\r\n* The app does not even connect to the log relay as no {{Start application log}}\r\n* This used to work in older versions of the SDK but now it is broken in all versions, which makes me believe it is similar to the above issue and not caused by a regression in Ti SDK but a behaviour change in the Windows emulators \r\n* I have attempted to run on older emulators but have run into TIMOB-23758 will try master and see if I can get anymore logging\r\n* Devices are not affected\r\n\r\nh5.Steps to reproduce\r\n\r\n# Build to a Windows 10 Mobile emulator {{appc run -p windows -T wp-emulator -C 10-0-1}}\r\n\r\nh5.Actual result\r\n\r\nNo logging \r\n\r\nh5.Expected result\r\n\r\nThere should be logging", "attachment": [ { "id": "60680", "filename": "hyperv-1.png", "author": { "name": "kiguchi", "key": "kota", "displayName": "Kota Iguchi", "active": false, "timeZone": "America/Los_Angeles" }, "created": "2016-11-11T03:29:48.000+0000", "size": 167382, "mimeType": "image/png" }, { "id": "60679", "filename": "hyperv-2.png", "author": { "name": "kiguchi", "key": "kota", "displayName": "Kota Iguchi", "active": false, "timeZone": "America/Los_Angeles" }, "created": "2016-11-11T03:29:48.000+0000", "size": 51158, "mimeType": "image/png" } ], "flagged": false, "summary": "Windows: No logging being received from Windows 10 Mobile Emulators", "creator": { "name": "eharris", "key": "eharris", "displayName": "Ewan Harris", "active": true, "timeZone": "Europe/Dublin" }, "subtasks": [], "reporter": { "name": "eharris", "key": "eharris", "displayName": "Ewan Harris", "active": true, "timeZone": "Europe/Dublin" }, "environment": "OS: Microsoft Windows 10 Pro 10.0.14393\r\nAppc core: 6.0.0-63\r\nAppc NPM: 4.2.8-9\r\nTi SDK: 6.0.0.v20161021034759", "closedSprints": [ { "id": 752, "state": "closed", "name": "2016 Sprint 23 SDK", "startDate": "2016-11-05T00:39:37.027Z", "endDate": "2016-11-19T01:39:00.000Z", "completeDate": "2016-11-29T06:51:57.887Z", "originBoardId": 114 } ], "comment": { "comments": [ { "id": "400755", "author": { "name": "kiguchi", "key": "kota", "displayName": "Kota Iguchi", "active": false, "timeZone": "America/Los_Angeles" }, "body": "I was able to reproduce this, I think this was caused because Hyper-V NAT network adapter only uses internal network. I was able to fix this by changing Hyper-V network switch to use external network like below:\r\n\r\n# Launch *Hyper-V Manager*\r\n# Select local machine and launch *Virtual Switch Manager*\r\n# Create new virtual network switch that uses *External network*\r\n# Return to *Hyper-V Manager* and select Windows Phone virtual machine\r\n# Select *Settings*, select *Emulator NAT Network Adapter* and then changes network adapter to use your external switch\r\n\r\n[^hyperv-1.png]\r\n\r\n[^hyperv-2.png]\r\n", "updateAuthor": { "name": "kiguchi", "key": "kota", "displayName": "Kota Iguchi", "active": false, "timeZone": "America/Los_Angeles" }, "created": "2016-11-11T03:29:51.000+0000", "updated": "2016-11-11T03:31:33.000+0000" }, { "id": "401093", "author": { "name": "kiguchi", "key": "kota", "displayName": "Kota Iguchi", "active": false, "timeZone": "America/Los_Angeles" }, "body": "I would resolve this ticket as not our bug and we might want to address this workaround in the docs later.", "updateAuthor": { "name": "kiguchi", "key": "kota", "displayName": "Kota Iguchi", "active": false, "timeZone": "America/Los_Angeles" }, "created": "2016-11-16T00:54:01.000+0000", "updated": "2016-11-16T00:54:01.000+0000" }, { "id": "406074", "author": { "name": "smohammed", "key": "smohammed", "displayName": "Samir Mohammed", "active": true, "timeZone": "America/Los_Angeles" }, "body": "Closing ticket as it is marked as \"Not Our Bug\"", "updateAuthor": { "name": "smohammed", "key": "smohammed", "displayName": "Samir Mohammed", "active": true, "timeZone": "America/Los_Angeles" }, "created": "2017-02-01T22:17:44.000+0000", "updated": "2017-02-01T22:17:44.000+0000" } ], "maxResults": 3, "total": 3, "startAt": 0 } } }