Chrome DevTools: Error is shown in Chrome's Console when try to console.trace()

Open

#1,315 opened on Mar 18, 2019 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language: C++
Stars: 563
Forks: 144
Avg merge: 10h 46m
Merged PRs (30d): 14

Description

Environment

Cross-platform modules:5.2.2
Android Runtime: tried these versions: 5.2.1, 5.2.0, 5.1.0, 5.0.0 and next

Describe the bug
Error is shown in Chrome DevTools Console when try to console.trace()

main-view-model.js:29 Trace
at HelloWorldModel.onTap (file:///data/data/org.nativescript.TestAppTr/files/app/main-view-model.js:29:17)
at Observable.notify (file:///data/data/org.nativescript.TestAppTr/files/app/tns_modules/tns-core-modules/data/observable/observable.js:107:32)
at Observable._emit (file:///data/data/org.nativescript.TestAppTr/files/app/tns_modules/tns-core-modules/data/observable/observable.js:127:18)
at ClickListenerImpl.onClick (file:///data/data/org.nativescript.TestAppTr/files/app/tns_modules/tns-core-modules/ui/button/button.js:26:23)

To Reproduce

tns create TestApp --ts
Add console.trace();
tns debug android
Open URL in Chrome and execute the code that calls console.trace();

Expected behavior
console.trace() call stack to be logged in Chrome DevTools Console

Sample project

Additional context
When tns run android the same content is logged by CLI.

Contributor guide

Open the contributing 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

Reproduce the issue with tns create TestApp --ts, tns debug android, and the console.trace() call, then compare Chrome DevTools output with the content logged by tns run android. Use the stack entries in main-view-model.js, observable.js, and button.js as the starting path. Done means the call stack is logged in Chrome DevTools Console without the reported error.

Written by the indexing model from the issue text.

Assessment

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