NativeScript / NativeScript/nativescript-cli

LiveSync related commands hang when devices for sync are disconnected

Open
#4,495 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug debug livesync run unit testing
Dominant language
JavaScript
Stars
1.1k
Forks
204
Avg merge
1d 9h
Merged PRs (30d)
8

Description

Environment
Provide version numbers for the following components (information can be retrieved by running tns info in your project folder or by inspecting the package.json of the project):

  • CLI: 5.3.0
  • Cross-platform modules: Not applicable
  • Android Runtime: Not applicable
  • iOS Runtime: Not applicable
  • Plugin(s):Not applicable

Describe the bug
Whenever all devices/emulators/simulators that we are using for LiveSync operation are disconnected or CLI is unable to sync changes on them, the command (tns debug, tns run, tns test...) should exit. Instead, it continues its execution and prepares the application.

To Reproduce

  1. Run tns run <platform>
  2. When the operation is running, disconnect all devices/stop all emulators/simulators on which you are syncing.
  3. Command should exit.
    Instead it continues its execution.

Expected behavior
Once all devices used for liveSync are disconnected (or we have errors when trying to sync on them), command should exit and does not give incorrect impression that it still liveSyncs your project.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Reproduce with tns run <platform>, then compare how tns debug, tns run, and tns test handle LiveSync when all devices, emulators, or simulators disconnect. Trace the LiveSync operation from the command entry point and verify that errors or loss of every sync target cause the command to exit instead of continuing preparation.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
cli, mobile
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
42/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.