Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Cannot use Chrome DevTools to debug a Tabris.js app #2069

Closed
cpetrov opened this issue May 27, 2020 · 3 comments
Closed

Cannot use Chrome DevTools to debug a Tabris.js app #2069

cpetrov opened this issue May 27, 2020 · 3 comments

Comments

@cpetrov
Copy link
Member

cpetrov commented May 27, 2020

Problem description

When using latest Chrome (83.0.4103.61) and Tabris.js (3.5.0) and trying to connect the debugger to a running Tabris.js app as described in the documentation:

To connect the Chrome DevTools to a Tabris.js app on the default port 9090, the following URL should be entered:

devtools://devtools/bundled/inspector.html?experiments=true&v8only=true&ws=<device-ip>:9090
(https://docs.tabris.com/latest/debug.html)

Exchange with the IP of your Android device.

... Chrome shows an empty page instead of the inspector UI. Following error is output to the console:

Uncaught (in promise) TypeError: Cannot assign to read only property 'length' of object '#<Storage>'
    at SettingsStorage.setPreference [as _setCallback] (host.js:106)
    at SettingsStorage.set (common.js:330)
    at VersionController._migrateSettingsFromLocalStorage (common.js:429)
    at VersionController._updateVersionFrom11To12 (common.js:396)
    at VersionController.updateVersion (common.js:366)
    at MainImpl._createSettings (main.js:37)
    at MainImpl._gotPreferences (main.js:34)
    at InspectorFrontendHostStub.getPreferences (host.js:105)
    at MainImpl._loaded (main.js:32)

Environment

  • Tabris.js version: 3.5.0
  • Device: ASUS X01BDA
  • OS: Android 9
@mpost
Copy link
Member

mpost commented Jun 3, 2020

Thanks for bringing it up. It works as expected in VSC and WebStorm. The chrome devtools have been tested as well. We will look into it.

@mpost mpost added this to the 3.6 milestone Jun 3, 2020
@oweitman
Copy link

oweitman commented Jun 11, 2020

Workaround: in chrome developer console goto Application, right click on local storage and clear.
Side effect: you loose your settings of cdt like breakpoints, etc.

@cpetrov
Copy link
Member Author

cpetrov commented Jun 18, 2020

The workaround is valid 👍

@cpetrov cpetrov closed this as completed Jun 18, 2020
@mpost mpost removed this from the 3.6 milestone Jun 18, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants