Titanium JIRA Archive
Titanium SDK/CLI (TIMOB)

[TIMOB-23664] LiveView: vEthernet network connection is selected when building on a Windows system

GitHub Issuen/a
TypeBug
PriorityHigh
StatusClosed
ResolutionWon't Fix
Resolution Date2017-05-19T15:28:03.000+0000
Affected Version/sRelease 5.4.0
Fix Version/sn/a
ComponentsLiveView, Windows
Labelsqe-5.4.0
ReporterEwan Harris
AssigneeGary Mathews
Created2016-07-20T15:58:58.000+0000
Updated2018-08-02T22:20:08.000+0000

Description

Description

When building on a Windows system that has Windows Phone Emulators installed LiveView seems to always pick the vEthernet (Internal Ethernet Port Windows Phone Emulator Internal Switch) network connection meaning that devices are unable to connect to the liveview server as this is an internal network connection used solely for emulators *Note* I believe that ipv4 address for this adapter is always 169.254.80.80 *Workaround* To workaround this issue, disable the switch in Network and Connections.

Go to Control Panel

Open Network and Sharing Centre

Click Change adapter settings

Right click vEthernet and click Disable

*This will mean you will not be able to build for Windows Phone Emulators, be sure to enable this when you are finished*

Steps to reproduce

Ensure you have Windows Phone Emulators installed and that you see the vEthernet switch in Network Connections

Enable LiveView from Studio

Build for Android

Disable the vEthernet switch in Network and Connections

Build for Android

Actual result

At step 3 the LiveView connection will not be successful At step 5 the LiveView connection will be successful

Expected result

The LiveView connection should be successful in both cases

Comments

  1. Chee Kiat Ng 2016-07-21

    [~cwilliams] any idea if this is a tooling or sdk ticket?
  2. Ewan Harris 2016-08-08

    Data that is returned from the require('os').networkInterfaces(); call. 
       { 'vEthernet (Internal Ethernet Port Windows Phone Emulator Internal Switch)':
   	   [ { address: 'fe80::5904:c643:ecad:cb59',
   	       netmask: 'ffff:ffff:ffff:ffff::',
   	       family: 'IPv6',
   	       mac: '00:15:5d:e2:da:13',
   	       scopeid: 8,
   	       internal: false },
   	     { address: '169.254.80.80',
   	       netmask: '255.255.0.0',
   	       family: 'IPv4',
   	       mac: '00:15:5d:e2:da:13',
   	       internal: false } ],
   	  Ethernet:
   	   [ { address: '2002:c0a8:140:1234:c0a2:4da3:84ac:3ba8',
   	       netmask: 'ffff:ffff:ffff:ffff::',
   	       family: 'IPv6',
   	       mac: 'd4:3d:7e:27:3c:02',
   	       scopeid: 0,
   	       internal: false },
   	     { address: '2002:c0a8:140:1234:cccc:97c4:8dd8:8006',
   	       netmask: 'ffff:ffff:ffff:ffff:ffff:ffff:ffff:ffff',
   	       family: 'IPv6',
   	       mac: 'd4:3d:7e:27:3c:02',
   	       scopeid: 0,
   	       internal: false },
   	     { address: 'fe80::c0a2:4da3:84ac:3ba8',
   	       netmask: 'ffff:ffff:ffff:ffff::',
   	       family: 'IPv6',
   	       mac: 'd4:3d:7e:27:3c:02',
   	       scopeid: 14,
   	       internal: false },
   	     { address: '192.168.2.2',
   	       netmask: '255.255.255.0',
   	       family: 'IPv4',
   	       mac: 'd4:3d:7e:27:3c:02',
   	       internal: false } ],
   	  'Loopback Pseudo-Interface 1':
   	   [ { address: '::1',
   	       netmask: 'ffff:ffff:ffff:ffff:ffff:ffff:ffff:ffff',
   	       family: 'IPv6',
   	       mac: '00:00:00:00:00:00',
   	       scopeid: 0,
   	       internal: true },
   	     { address: '127.0.0.1',
   	       netmask: '255.0.0.0',
   	       family: 'IPv4',
   	       mac: '00:00:00:00:00:00',
   	       internal: true } ] }
  3. Gary Mathews 2016-08-09

    master: https://github.com/appcelerator/liveview/pull/94
  4. Samir Mohammed 2017-02-01

    Verified fix, was able to use LiveView with the vEthernet network connection enabled and disabled. *Environment* 
       Phone : Nexus 6P
   Emulator: Android 6.0.0 ARM
   APPC studio version: 4.9.0.201701181905 (Nightly) 
   
   Operating System:
   Name                        = Microsoft Windows 10 Pro
   Version                     = 10.0.14393
   Architecture                = 32bit
   
    CPUs                      = 4
    
   Memory                      = 17034395648
    
   Node.js:
   Node.js Version             = 4.6.0 
   npm Version                 = 2.15.9
    
   Titanium SDK:
   SDK Version                 =  6.1.0.v20170131075226
  5. Ewan Harris 2017-05-19

    The fix made for this ticket was reverted in https://github.com/appcelerator/liveview/pull/99 in favour of passing the IP via the means added in CLI-1075. Therefore I am closing this ticket as Wont Fix To do this

    From the CLI

    When building, pass in the --liveview-ip <IP> where IP is the IP address you wish to use. This option is in addition to the --liveview flag

    From Studio

    Open Preferences

    #* On MacOS Appcelerator Studio -> Preferences #* On Windows Windows -> Preferences

    Expand the Studio section

    Click LiveView

    Set the LiveView Host field as the IP you wish to use

    Generally, when building to a physical device on Windows the IP used should be the IP of the development machine, and when building to a Windows Mobile Emulator the IP address for Internal Ethernet Port Windows Phone Emulator Internal Switch should be used.
  6. Eric Merriman 2018-08-02

    Closing old "Won't fix" tickets. If you disagree, please reopen.

JSON Source