Titanium JIRA Archive
Titanium SDK/CLI (TIMOB)

[TIMOB-24062] Windows: No logging being received from Windows 10 Mobile Emulators

GitHub Issuen/a
TypeBug
PriorityHigh
StatusClosed
ResolutionNot Our Bug
Resolution Date2016-11-16T00:54:01.000+0000
Affected Version/sRelease 6.0.0
Fix Version/sRelease 6.1.0
ComponentsWindows
Labelsqe-6.0.0
ReporterEwan Harris
AssigneeKota Iguchi
Created2016-10-21T14:08:45.000+0000
Updated2017-02-01T22:18:52.000+0000

Description

Description

When 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 * The app does not even connect to the log relay as no Start application log * 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 * 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 * Devices are not affected

Steps to reproduce

Build to a Windows 10 Mobile emulator appc run -p windows -T wp-emulator -C 10-0-1

Actual result

No logging

Expected result

There should be logging

Attachments

FileDateSize
hyperv-1.png2016-11-11T03:29:48.000+0000167382
hyperv-2.png2016-11-11T03:29:48.000+000051158

Comments

  1. Kota Iguchi 2016-11-11

    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:

    Launch *Hyper-V Manager*

    Select local machine and launch *Virtual Switch Manager*

    Create new virtual network switch that uses *External network*

    Return to *Hyper-V Manager* and select Windows Phone virtual machine

    Select *Settings*, select *Emulator NAT Network Adapter* and then changes network adapter to use your external switch

    [^hyperv-1.png] [^hyperv-2.png]
  2. Kota Iguchi 2016-11-16

    I would resolve this ticket as not our bug and we might want to address this workaround in the docs later.
  3. Samir Mohammed 2017-02-01

    Closing ticket as it is marked as "Not Our Bug"

JSON Source