NativeScript / NativeScript/nativescript-cli
cli issues : env.uglify breaks console.log / hmr / debugger cannot connect device
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 1.1k
- Forks
- 204
- Avg merge
- 1d 9h
- Merged PRs (30d)
- 8
Description
Environment
✔ Component nativescript has 7.0.11 version and is up to date.
✔ Component @nativescript/core has 7.0.12 version and is up to date.
✔ Component @nativescript/ios has 7.0.4 version and is up to date.
✔ Component @nativescript/android has 7.0.1 version and is up to date.
✔ Xcode version 12.1.0 satisfies minimum required version 10.
Describe the bug
I have several issues when deploying the app
Using the emulator :
- when I use the
--env.uglifyflag, console.log messages are not shown in the console. - when I have HMR active, the app closes after it launched. I have to manually start it to use it.
- navigating to
devtools://devtools/bundled/inspector.html?ws=localhost:41000gives a timeout :
Cannot connect to device socket. The error message is 'Timeout while waiting for lock "/Users//.local/share/.nativescript-cli/abb5c8da9f657a0090e2668a3a72a99b"'.
NativeScript debugger was not able to get inspector socket port on device 6F98B19F-AC48-4CE6-917C-590F22F2559B for application org.nativescript.foo.
Cannot connect to device socket. The error message is 'Device socket port cannot be found.'.
To Reproduce
- create a new ns Angular project with
ns create foo --ng - open
items.component.tsand add the lineconsole.log('NS rules!');tongOnInit - run the project with :
ns debug ios--> You see the added log message - run the project with :
ns debug ios --env.uglify- the app closes after it is started --> not correct
- start the app yourself manually, notice you don't see the added log message --> not correct
- run the project with :
ns debug ios --env.uglify --no-hmr--> the app does not close after it starts correct - navigate to
devtools://devtools/bundled/inspector.html?ws=localhost:41000
Sample project
See 'To Reproduce'
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the behavior with ns debug ios, --env.uglify, and --no-hmr, using the console.log added to items.component.ts. Then inspect the CLI entry points involved in HMR, uglification, and the debugger connection to the inspector URL. Done means uglified runs retain console output, HMR does not close the app, and the debugger connects to the device.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ios, javascript
- Domain
- cli, devtools, mobile-dev
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100