Scratch Link exits with "RFCOMM run loop exited"

[ericrosenbaum]

After connecting and disconnecting successfully several times, we saw this error on the Scratch Link console: RFCOMM run loop exited,

and this error on the Scratch console:

Uncaught (in promise) code: -32601 data: "Cannot call send in discovery state" message: "Method Not Found" (many times)

this causes Scratch Link to exit, which causes:

BTSession error: {"code":-32500,"data":"Connection process could not start or channel was not found","message":"Server Error"} (once)

[haworthia]

This looks like a failure to connect to the BT device.

The RFCOMM run loop exits when the device disconnects, so I'm guessing you will see that message several times in the Scratch Link console if you connect and disconnect successfully several times. If an attempt to connect to EV3 is not successful, Scratch Link responds with "Connection process could not start or channel was not found". The "Cannot call send in discovery state" happens when you try to send a command when there is no device connected.

Honestly EV3 Bluetooth is not the best experience all the time, and the device might refuse to connect, in which case Scratch Link should allow you to try to connect again.

Does Scratch Link tell you that connection was successful? And then is it unreachable after you see those errors?

[cwillisf]

I haven't seen this in quite a while... I'm closing it until/unless we can repro.

@ericrosenbaum and @evhan55, do you think this is still a problem? Can you reproduce this behavior? If so, please reopen this issue. Thanks!

[evhan55]

I haven't seen it in a while, either! If I run into it again, in a reproducible way, I can reopen the issue.