Hello Rocket.Chat community,
I am facing a persistent issue with the official Android mobile application (v4.78.0) where downloading or opening PDF files fails immediately with the error “Error while downloading file”.
Environment Details:
-
Server OS: Ubuntu host running via Docker
-
Rocket.Chat Version: 8.9.0
-
Reverse Proxy: Traefik (with valid Let’s Encrypt SSL, full certificate chain verified,
Verify return code: 0) -
Mobile Client: Official Rocket.Chat Android App v4.78.0 on Samsung S25 Ultra (Android 17 / One UI)
What works:
-
Downloading and viewing PDFs works perfectly fine on Windows Desktop App, desktop browsers, and mobile Chrome browser (both via Wi-Fi and 4G/5G).
-
curlrequests to the file URL returnHTTP/1.1 200 OKwith proper headers (Content-Disposition: inline, correctContent-Type: application/pdf).
What we have already tried / checked:
-
Disabled
Protect Uploaded Files,Restrict files to rooms' members, and JWT/CSP restrictions in Workspace Settings. -
Added Traefik middleware to strip unwanted
Content-Security-Policyheaders and forcedContent-Disposition: inline. -
Tried clearing local server cache and clearing app data on Android.
-
Tested on both mobile data (4G/5G) and Wi-Fi.
-
Even tested via the official Android app, but the native client fails to download/preview the file (no network request hits Traefik/server at all when triggered from the chat stream).
It seems like the native React Native / Expo FileSystem downloader on Android 17 fails to handle the file storage interaction or stream negotiation. Has anyone encountered this or found a workaround for Android clients?
Thank you for your support!
Server Setup Information
- Version of Rocket.Chat Server: 8.9.0
- Operating System: Ubuntu Linux (Docker Host)
- Deployment Method: Docker Compose (Traefik + Rocketchat + MongoDB)
- Number of Running Instances: 1
- DB Replicaset Oplog: Enabled (Standard Docker MongoDB setup)
- NodeJS Version: v24.15.0
- MongoDB Version: 7.0.32 / wiredTiger
- Proxy: Traefik v3.4 (Let’s encrypt - custom headers)
- Firewalls involved: Standard UFW / Router firewall (Port 80 and 443 open)