Skip to content

Latest commit

 

History

History
69 lines (65 loc) · 2.49 KB

device_configuration.md

File metadata and controls

69 lines (65 loc) · 2.49 KB

device-configuration.json

Device configuration file provides means to define multiple target devices. Target devices can be passed to npm scripts via their name forgoing need for manual target device switching via Device and Certificate Managers.

device-configuration.json should be placed in application root folder. Optional fields can be omitted from file.

[
  {
    "name": String,
    "target": String,
    "port": Number,
    "profile": String,
    "chrome": String
  }
]

Field description

name required User friendly device name. Passed to npm scripts as device name identifier. Must be unique.
target required IP address of target device. Specified as IP or IP:Port.

Defaults to port 26101 when not specified.
port optional Local debug port to be used for communication between Chrome DevTools and an application being debugged on target device.

Defaults to port 9666 when not specified.

Setting up different ports for devices, allows running concurrent DevTools instances on multiple devices.
profile optional Certificate profile name to be used when signing device package for this device. Certificate profile needs to be defined in Certificate Manager.

If not specified, active certificate profile will be used.
chrome optional Path to Chrome executable to be used as DevTools client.

If not specified, DevTools frontend will be opened in default browser.

TV Devices run different versions of Web Engine, model year dependant. When utilizing chrome executable as DevTools client, using version matching target device may yield best experience.