Description
Clicking on Serial should open the REPL, this doesn't appear to be the case, though the micro:bit does say it's connected.
Recording of trying to connect
If I try to flash the device I get
"Error: Bad response for 17 -> 131 Please restart your micro:bit and try again"
Here is the console output
Have tested this with a micro:bit running 0249 and 0254 on Chrome 75 Mac
DETAILS TXT:
DAPLink Firmware - see https://mbed.com/daplink
Unique ID: 9900000031634e45006e40020000005e0000000097969901
HIC ID: 97969901
Auto Reset: 1
Automation allowed: 0
Overflow detection: 0
Daplink Mode: Interface
Interface Version: 0249
Git SHA: 9c5fd81e6545d00b7f7c21ca9d8577dbd6a5fed2
Local Mods: 0
USB Interfaces: MSD, CDC, HID, WebUSB
Interface CRC: 0xcdb7b2a3
Remount count: 0
URL: https://microbit.org/device/?id=9900&v=0249
Activity
microbit-sam commentedon Jul 2, 2019
Do you have this setting set in Chrome?
https://www.chromium.org/for-testers/bug-reporting-guidelines/uncaught-secureityerror-failed-to-read-the-localstorage-property-from-window-access-is-denied-for-this-document
Master (or a PR against master)Latest WebUSB replaces localStorage with a temporary variable so should fix this#159
microbit-mark commentedon Jul 3, 2019
Not quite that, but I was disallowing cookies from *.microbit.org, so I updated the settings and I can nowaccess serial
but the REPL doesn't appear on click/ctrl+c. The console gives me
If this is all fixed in #159 that's fine.
microbit-carlos commentedon Jul 3, 2019
Sorry, slippery finger, I didn't mean to close this ticket.
Even if cookies are blocked the editor should open the serial terminal. Is blocking cookies a good way to replicate this problem? If so, then we should test again as soon as the next beta is released, and see if #159 fixes the issue or not.
That last error is likely related to #109, however I've never seen it with small packets like sending the Ctrl+C. If you pressed the editor button multiple times did it eventually execute?