Whenever trying to attach a picture of “larger” size (anything over 1MB, it appears; haven’t narrowed it down further) to a post in a Discourse forum while using a mobile Chrome based browser (Chrome, Cromite, Brave), uploads fail. They do work in Firefox.
The upload is supposedly initiated and the status message is stuck at “Processing upload” - but the upload never starts (no progress) and things remain stuck there forever. In some cases, the upload is never even initiated, and the interface goes back to the editing interface as if the upload was never attempted.
OS: Pixel 9 Pro with GrapheneOS (Android 15). Adaway (host based ad blocking) in VPN mode is used but appears to not make any difference (Firefox works regardless of whether this is active or not, Chrome based browsers fail regardless). It also happens on any uplink I’ve been able to test (all WiFi and two different mobile data providers).
I’ve narrowed it down to the client preprocessing media-optimization-worker.js javascript not getting loaded:
The fetch request is canceled for an unknown reason. For smaller pictures, where this media-optimization-worker is not being used due to already small enough, everything works as expected. In mobile Firefox it works in all cases (but Discourse UI is still very screwed up in mobile Firefox, so…).
I’m experiencing this as a client, I don’t operate any Discourse myself. But since it happens on both the one Discourse instance I use as a user (horlogeforum.nl, operated by a professional Discourse hosting partner) and try.discourse.org I would assume those settings are properly done.
It also doesn’t happen in Firefox, so if a change would be causing this I’d expect everything to fail…
From what I can tell in the debug logs, the issue appears to be that the media-optimization-worker.js javascript itself does not succeed in loading; the UI never even attempts an actual upload.
You need to liaise with the specific forum admin then I suggest, as the back end needs to be configured to accommodate large file sizes. That would help isolate the issue (not saying it’s not an issue)
The fact that large uploads are being resized on the client is not the issue in itself as this works fine in Firefox. The javascript doing it, fails to load in Chrome based browsers.
The most common reason for a request to be ‘cancelled’ this fast is a browser extension (e.g. adblocker, etc.). Could you double check whether you have anything like that enabled? And also check to see if the same problem happens in incognito mode?
FWIW, I’m able to upload large images using Chrome with no problems. The media-optimization-worker.js file loads successfully.
