Title: Node Inspector takes too long to list the sources for debugging · Issue #413 · NativeScript/android · GitHub
Open Graph Title: Node Inspector takes too long to list the sources for debugging · Issue #413 · NativeScript/android
X Title: Node Inspector takes too long to list the sources for debugging · Issue #413 · NativeScript/android
Description: Here is how to reproduce the problem with the NativeScript CLI: tns create test cd test tns platform add android tns debug android --start After executing the above commands from the command prompt, Node Inspector opens in a browser, but...
Open Graph Description: Here is how to reproduce the problem with the NativeScript CLI: tns create test cd test tns platform add android tns debug android --start After executing the above commands from the command prompt...
X Description: Here is how to reproduce the problem with the NativeScript CLI: tns create test cd test tns platform add android tns debug android --start After executing the above commands from the command prompt...
Opengraph URL: https://github.com/NativeScript/android/issues/413
X: @github
Domain: github.com
{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Node Inspector takes too long to list the sources for debugging","articleBody":"Here is how to reproduce the problem with the NativeScript CLI:\n\n```\ntns create test\ncd test\ntns platform add android\ntns debug android --start\n```\n\nAfter executing the above commands from the command prompt, Node Inspector opens in a browser, but shows nothing in the sources tab for debugging. If the user has enough patience to wait a minute or two, the sources tab would eventually fill with the scripts on the device. The problem is that from the user's point of view the debugging experience is broken. In fact most people seeing this behavior would simply decide the debugger is not working at all. The same misbehavior can be observed in AppBuilder as well. When launching the debugger in Visual Studio all breakpoints appear as disabled and if the user interacts with the application they are not hit. After waiting for a while, the breakpoints would be enabled and debugging can proceed as expected, but again the users would just assume the debugger is not working.\nAfter some investigation on our side, it appears that the `scriptParsed` notifications from Node Inspector are received after a very long delay. There is also an error in the console saying:\n\n```\nPage.getResourceTree failed.\nReferenceError: process is not defined\n```\n\nPlease, note that both Chrome Debug Tools and Visual Studio Debugger need to invoke `getResourceTree` to populate the resources for debug. Evidently, `getResourceTree` fails for some reason, however both debuggers still manage to populate the scripts, because some `scriptParsed` notifications are received after some time. However, according to our tests, if `getResourceTree` is not called, no `scriptParsed` notifications are received at all.\n","author":{"url":"https://github.com/vanka78bg","@type":"Person","name":"vanka78bg"},"datePublished":"2016-04-07T15:25:54Z","url":"https://github.com/NativeScript/android/issues/413"}
| react-profiling | 0 |
| react-import-map | react,react-dom,react-dom/client,react-dom/profiling,react-is,react/compiler-runtime,react/jsx-dev-runtime,react/jsx-runtime,scheduler@b8488ee2c322 |
| route-pattern | /_view_fragments/issues/show/:user_id/:repository/:id/issue_layout(.:format) |
| route-controller | voltron_issues_fragments |
| route-action | issue_layout |
| fetch-nonce | v2:fd1fee05-4135-60b4-3701-5321775ca0ec |
| current-catalog-service-hash | 81bb79d38c15960b92d99bca9288a9108c7a47b18f2423d0f6438c5b7bcd2114 |
| request-id | 8EEE:4BB79:11D903F:16C946B:6B01200B |
| html-safe-nonce | bf02aafe5ef3d5a2b0776c3410099c44f57fa8d1e4f852fc656c101baf499651 |
| visitor-payload | eyJyZWZlcnJlciI6IiIsInJlcXVlc3RfaWQiOiI4RUVFOjRCQjc5OjExRDkwM0Y6MTZDOTQ2Qjo2QjAxMjAwQiIsInZpc2l0b3JfaWQiOiI4NDc3NDI2MTIxNTkwMjUxNTMxIiwicmVnaW9uX2VkZ2UiOiJpYWQiLCJyZWdpb25fcmVuZGVyIjoiaWFkIn0= |
| visitor-hmac | 29491649ccf8e793dd6fb98efa06767399f45cf5bc04f2a2bbeef7ea2817d04c |
| hovercard-subject-tag | issue:146658460 |
| github-keyboard-shortcuts | repository,issues,copilot |
| google-site-verification | Apib7-x98H0j5cPqHWwSMm6dNU4GmODRoqxLiDzdx9I |
| octolytics-url | https://collector.github.com/github/collect |
| analytics-location | / |
| fb:app_id | 1401488693436528 |
| apple-itunes-app | app-id=1477376905, app-argument=https://github.com/_view_fragments/issues/show/NativeScript/android/413/issue_layout |
| twitter:image | https://opengraph.githubassets.com/a589a3c2ed9da32fdd939d416a8d417dbac8492febdbac755571f02fd23a767c/NativeScript/android/issues/413 |
| twitter:card | summary_large_image |
| og:image | https://opengraph.githubassets.com/a589a3c2ed9da32fdd939d416a8d417dbac8492febdbac755571f02fd23a767c/NativeScript/android/issues/413 |
| og:image:alt | Here is how to reproduce the problem with the NativeScript CLI: tns create test cd test tns platform add android tns debug android --start After executing the above commands from the command prompt... |
| og:image:width | 1200 |
| og:image:height | 600 |
| og:site_name | GitHub |
| og:type | object |
| og:author:username | vanka78bg |
| hostname | github.com |
| expected-hostname | github.com |
| None | cc5dfdd32f62ebd3223cab3af3aa2b268d3605218237326a48a99d1efd89495c |
| turbo-cache-control | no-preview |
| go-import | github.com/NativeScript/android git https://github.com/NativeScript/android.git |
| octolytics-dimension-user_id | 7392261 |
| octolytics-dimension-user_login | NativeScript |
| octolytics-dimension-repository_id | 29137950 |
| octolytics-dimension-repository_nwo | NativeScript/android |
| octolytics-dimension-repository_public | true |
| octolytics-dimension-repository_is_fork | false |
| octolytics-dimension-repository_network_root_id | 29137950 |
| octolytics-dimension-repository_network_root_nwo | NativeScript/android |
| turbo-body-classes | logged-out env-production page-responsive |
| disable-turbo | false |
| browser-stats-url | https://api.github.com/_private/browser/stats |
| browser-errors-url | https://api.github.com/_private/browser/errors |
| release | 8c77c9e8439031ad54c75a250694842892f693e1 |
| ui-target | full |
| theme-color | #1e2327 |
| color-scheme | light dark |
| react-app-name | issues |
Links:
Viewport: width=device-width