1210801 - Error opening input stream while launching WebIDE, device connection fails

Status: RESOLVED WORKSFORME

(DevTools Graveyard :: WebIDE, defect)

Description

[Jack W]

User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:43.0) Gecko/20100101 Firefox/43.0
Build ID: 20151001004012

Steps to reproduce:

Enable WebIDE error logging as per https://developer.mozilla.org/en-US/docs/Tools/WebIDE/Troubleshooting#Enable_logging then open the browser console followed by the WebIDE


Actual results:

'Error opening input stream (invalid filename?): resource://gre/components/TCPSocket.js: undefined' is logged to the browser console, and the WebIDE is then unable to connect to any devices over USB or WiFi (chrome is able to connect successfully, and adb devices works correctly).


Expected results:

No errors should have been logged to the console, and the WebIDE should be able to connect to devices over WiFi and USB.

Comment 1

[J. Ryan Stinnett [:jryans] (Use needinfo, replies may be slow)]

Firefox 43 has been waiting for bug 1207090 to be uplifted.  That was done today, so I would expect it to work after the next 43 update.

Can you check again after that and let me know what happens?

Comment 2

[Jack W]

USB debugging is now working, and no errors are being logged to the console when WebIDE is launched. However, my device (Nexus 5 running Android 5.1.1 with Firefox Aurora 43.0a2) still isn't showing up in wifi debugging pane, with wifi debugging enabled on the device.

Comment 3

[J. Ryan Stinnett [:jryans] (Use needinfo, replies may be slow)]

This may sound a little silly, but what happens if you try:

1. Make sure WebIDE is closed
2. Open Firefox on Android device
3. Verify WiFi debugging enabled
4. Open WebIDE

WebIDE is currently only scanning for devices on open in 43+, we need to add a "refresh" devices button, so maybe these steps will help.

Comment 4

[Jack W]

No - even with build 2015-10-06 on mobile and desktop, it's not working.

Comment 5

[J. Ryan Stinnett [:jryans] (Use needinfo, replies may be slow)]

Has WiFi debugging ever worked for you in the past?  Your initial report was about an error in USB debugging, so I wasn't sure if WiFi debugging is a regression as well, or it has just never worked at all.

Comment 6

[Jack W]

I've never tried to use it in the past, so I don't know if it ever worked. I've just tried installing nightly on my computer and beta on my phone, and that combination isn't working either. Computer is connected via ethernet and phone over wifi, but they are able to talk to one another normally (running a web server from my computer functions as expected).

Comment 7

[J. Ryan Stinnett [:jryans] (Use needinfo, replies may be slow)]

(In reply to jackwickham from comment #6)
> I've never tried to use it in the past, so I don't know if it ever worked.
> I've just tried installing nightly on my computer and beta on my phone, and
> that combination isn't working either. Computer is connected via ethernet
> and phone over wifi, but they are able to talk to one another normally
> (running a web server from my computer functions as expected).

Hmm... that could indeed be the issue.  Discovery of devices for WiFi uses multicast packets, which are fairly rare these days.  Most routers do not send them across different interfaces.  They don't travel multiple network hops, either.  Additionally, some routers are buggy / just drop them.

Can you re-test with the computer and device both using WiFi connection to the same WiFi router (no ethernet used)?

Comment 8

[Jack W]

WiFi debugging functions correctly on my laptop, so it looks like it is just that my router isn't allowing those packets through.

Comment 9

[J. Ryan Stinnett [:jryans] (Use needinfo, replies may be slow)]

Okay, great!  I think that's the best we can do for the moment.  I'm not aware of a way we can force the discovery to travel further without totally redesigning things.

Thanks for filing the bug, I'm glad we got these worked out!