NativeScript / NativeScript/nativescript-cli

debug android --debug-brk do not stop if app is not deployed

Open
#4,567 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug debug severity: low
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.1
  • Cross-platform modules: 5.3
  • Android Runtime: 5.3
  • iOS Runtime: 5.3
  • Plugin(s): No

Describe the bug
tns debug android --debug-brk do not stop on first line if app is not previously deployed.

To Reproduce

tns create TestApp --js
tns debug android --debug-brk --path TestApp

Expected behavior
debug android --debug-brk to stop on first line of code.

Additional context
No issues with command above if tns run android is executed before that (app is available on device).

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

Start by reproducing the behavior with tns create TestApp --js and tns debug android --debug-brk --path TestApp, then compare it with a run after tns run android. Trace the debug android command's handling of an undeployed app; done means --debug-brk stops on the first line without requiring a prior deployment.

Written by the indexing model from the issue text.

Assessment

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.