I’m reporting an issue with the file upload functionality via the Bricks form element. This issue seems to only exist on Android mobile devices (Chrome browser) and has occurred fairly recently (older versions, roughly 3-5 months ago, worked fine). Desktop(chrome) and iOS (Chrome) seem to work fine too.
Issue:
Users submit a form with uploaded files (pictures). After checkout, the submission enters an endless loop, and the data (including files) never reaches the backend. I’ve implemented logging, Chrome logs the error ERR_UPLOAD_FILE_CHANGED.
The error only occurs when files are selected via the default upload interface (e.g., gallery/pictures).
Workaround: If users select the same files via the native file browser (e.g., via the three-dash menu > “Browse” > selects “Camera” storage), the upload succeeds without errors.
The Bricks Form Element might trigger a file picker that references unstable file paths (e.g., temporary folders), which Chrome cannot handle consistently during upload. The “Camera” folder path appears to provide stable file references.
Questions:
Is this bug already known? Are there patches or fixes planned?
Can the form be configured to prioritize direct file system access (e.g., defaulting to the “Camera” folder) to avoid path-related conflicts?
This issue is blocking the core feature of my website – any updates or temporary solutions would be greatly appreciated. I’m happy to provide logs or example URLs if needed.
I tested locally, but I could not replicate this issue. Probably I’m testing wrong, so if you can share a link to a form, where I can test this, it would be great.
Additional, can you test with the older Bricks version, just to confirm that the change was really in the recent ones? As for now, I don’t have any change at the top of my head, that we made in the form element, that could cause this.
Thanks for your reply.
I’ve sent you access information for a staging copy via PM. Please let me know if you need more information and how to proceed.
As an aside, the issue may be related to chrome on android. If I compare the file upload function in Bricks’ form element to other file hosting services (e.g. transferxl, transfernow, etc.), they trigger a different native upload interface for uploading data (no problems for me there on the same phone, same browser, same network) than the one triggered by Bricks’ form element, e.g. see here:
When I select "Medien-Auswahl (“Media Selection”), it takes me directly to the “Camera” folder path, which I described as a workaround in my original post. This means that the initial view of images provided by Bricks form element, which seems to be unstable, is not accessible there at all there. In addition, I can directly select the “camera” there, which opens the camera interface - this is also no longer possible in the Forms element (I remember that this was the case earlier, but cannot point you to a specific version of Bricks when this last worked).
I never got the confirmation, but at least in my testing, it appears that the Chrome will automatically change the file picker type based on an allowed file formats.
