Repository navigation
Web Workflow unable to write code.py #10762
Description
CircuitPython version and board name
Adafruit CircuitPython 10.0.3 on 2025-10-17; Adafruit Feather ESP32-S3 TFT with ESP32S3
Board ID:adafruit_feather_esp32s3_tftCode/REPL
print("Hello World!")Behavior
- Set up web workflow in settings.toml
- Connect to board in the browser and enter the File Editor
- Click edit next to code.py
- Click save
- Loading Status is 500 (Internal Server Error)
Description
This should return a status of 200 or 204
Additional information
I haven't tested with other files yet
Activity
[-]Web Workflow unable to write files[/-][+]Web Workflow unable to write code.py[/+]makermelissa commentedon Dec 22, 2025
This works as intended with CircuitPython 9.2.9, so this is broken as of version 10.
tannewt commentedon Jan 13, 2026
I think the S3 at least has some web workflow issues. On the ESP32 it's been very snappy for me.
tannewt commentedon Jan 13, 2026
More info here: https://forums.adafruit.com/viewtopic.php?p=1078149
makermelissa commentedon Jan 13, 2026
Ok, cool. I'm just using 9.2.9 for now.
deisterhold commentedon Jan 24, 2026
Running into this issue as well.
When using a Lilygo T Dongle S3 plugged into a USB power brick, I'm receiving a
USB storage active.message when trying to create a folder named 'test' on the drive.Looking through the code it looks like the file system is locked here and bubbles up as a
FR_WRITE_PROTECTEDerror.davs2rt commentedon Mar 31, 2026
Since https://forums.adafruit.com/viewtopic.php?p=1078149 is locked, I'm replying (much delayed) here. I have a bunch of Seeedstudio ESP32-C3 exhibiting the web workflow failures, but have also seen this on an Adafruit Feather (forget which one) in teaching CPy.
bmorgenthaler commentedon Apr 16, 2026
Running into the same issue with version 10.1.4 on multiple M5 Stack AtomS3U usb sticks.
dhalbert commentedon May 19, 2026
@makermelissa I'm confused, is this still present, or is this an editor issue? Thanks.
dhalbert commentedon Jun 28, 2026
I think this was fixed by #11048.