Right now when you try to connect a physical device to WebIDE you only have one way to diagnose if it worked: it either works or it doesn't, but if it doesn't you're left on the dark as to why it didn't work. It would be amazing to show a list of the things ADB helper is trying to do to connect, and what happened, so we can diagnose what the h... is going on. Specially with weird computers and configurations!
We could have another button or something to bring up the ADB Helper logs (bug 1000309) when there is an error.
Depends on: 1000309
Summary: Provide more debug info for connection errors? → Expose ADB Helper logs after connection error
You can see some information via the browser console, Ctrl-Shift-J on Windows As this is for developers, all the logs from Valence/WebIDE connecting could be displayed on the initially WebIDE blank screen
About:debugging bug triage. Filter on TRIAGE-JD201705 Temporarily setting P3 to bugs migrated from webide to cleanup the triage for about:debugging.
Priority: -- → P3
You need to log in before you can comment on or make changes to this bug.