Carlos Pereira Atencio

@abchatra The general idea of the workaround (from https://github.com/microbit-foundation/DAPLink/issues/17#issuecomment-1555034429): * When the response for the wrong DAP command is received, start tracking a history of received and expected commands *...

We talked about it with @abchatra and we think we should first do the following: - Detect the issue and add it to the metrics - Create a UX workflow...

An extension could be made calling the `uBit.power.getPowerSource()` C++ function. https://github.com/lancaster-university/codal-microbit-v2/blob/v0.2.66/inc/MicroBitPowerManager.h#L196-L203 One thing to keep in mind is that there is an issue, where battery power cannot be correctly detected...

@microbit-katie has found that disabling the accessible blocks experimental feature resolved the issue, so it looks like that might be the culprit. I've tried this as well and it has...

While disabling the accessible blocks feature resolves the problem when the blocky toolbox and workspace don't load, the issue I still have where projects cannot be loaded at all, still...

Were you able to look into the other issue @riknoll ? I still have the beta session with broken projects, in case it's useful for debugging.

Not quite, as it's not only with projects I tried to open with the keyboard nav experiment, but I believe with all existing projects that existed at the time, even...

And trying top open the project in a new tab:

Test URL: https://makecode.microbit.org/app/9e68ab5b69437da8618b123bbf54da06577932a0-8bcd77d1ac

I think there are two different parts to this: 1. We have a long press event and an extension to use it 2. Because of the long press feature, when...