Bump @adafruit/ble-file-transfer-js to 1.0.5#478
Merged
makermelissa merged 1 commit intoApr 28, 2026
Merged
Conversation
Picks up the renamed status constant and corrected user-facing message from adafruit/ble-file-transfer-js#10: STATUS_ERROR_USB_MOUNTED (0x05) -> STATUS_ERROR_READONLY "Unable to write while USB connected" -> "Filesystem is read-only" The CircuitPython firmware returns 0x05 whenever filesystem_lock() fails, not specifically when a USB host is connected. The old label was confusing for users on wall power who saw the USB message even with no host attached.
makermelissa
approved these changes
Apr 28, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Picks up adafruit/ble-file-transfer-js#10, which corrects a long-standing mislabeled status code in the BLE File Transfer client.
What changed upstream
CircuitPython firmware returns status code
0x05wheneverfilesystem_lock()fails, not specifically when a USB host is connected. Seesupervisor/shared/bluetooth/file_transfer_protocol.h:The library was labeling that status
STATUS_ERROR_USB_MOUNTEDand rejecting with "Unable to write while USB connected" / "Unable to read while USB connected". 1.0.5 renames the constant toSTATUS_ERROR_READONLYand reworks the user-facing message to "Filesystem is read-only", which accurately covers any case where the FS can't be locked for writes (host MSC mount, device-side read-only mount, etc.).Why this matters for web-editor
Users running on wall power with no host attached have been seeing "Unable to write while USB connected" when they try to rename, write, or delete files. The new message tells them what's actually going on.
Risk
Low — pure dependency bump with a friendlier error string. Tested locally with
npm run build(clean build, no warnings beyond the existing vite plugin-timings notice).Independent of #475.