Repository navigation
Regression in 3.34.0.1: Android Storage Access Framework (DocumentProvider) cannot create files ("Unable to save document") #17336
Description
⚠️ Before posting ⚠️
- This is a bug, not a question or an enhancement.
- I've searched for similar issues and didn't find a duplicate.
- I've written a clear and descriptive title for this issue, not just "Bug" or "Crash".
- I agree to follow Nextcloud's Code of Conduct.
Steps to reproduce
- Open an email with a PDF attachment.
- Tap "Save".
- Choose "Save to".
- Select Nextcloud from the Android document picker.
- Choose any folder.
- Tap Save.
Regression
Version 3.34.0.0 (June 8, 2026): OK
Version 3.34.0.1 (June 24, 2026): BROKEN
Downgrading from 3.34.0.1 to 3.34.0.0 immediately restores the ability to save files through Android's "Save to" dialog without any other changes.
Expected behaviour
The PDF should be saved into the selected Nextcloud folder.
Actual behaviour
Android displays:
"Unable to save document."
The file is not created.
Android version
16
Device brand and model
Motorola Edge 50 Pro
Stock or custom OS?
Stock
Nextcloud android app version
34.0.1
Nextcloud server version
34.0.1
Using a reverse proxy?
No
Android logs
No response
Server error logs
Additional information
- Uploading files directly from the Nextcloud app works correctly.
- Browsing files inside the Nextcloud app works correctly.
- The problem only occurs when another app uses the Android Storage Access Framework (DocumentProvider).
- Clearing app data/cache and reinstalling the app does not help.
- Granting "Manage all files" permission does not help.
- Downgrading to the previous Android app version fixes the problem immediately.
This appears to be a regression in the DocumentProvider implementation.
Activity
ttrubep1 commentedon Jul 20, 2026
I have the same problem, but with one minor difference:
I gave several apps access to a Nextcloud directory so that they can regularly store backups there which are then automatically uploaded to my Nextcloud instance – as a local backup is obviously useless if the phone gets lost…
Currently, the backup files are created on my Nextcloud, but the apps trying to store the backup report an error (backup directory inacessible) and the file size remains at 0 byte.
I can confirm that this is a regression as it worked before the last update.
AntonLydike commentedon Jul 26, 2026
I am running into the same bug, same issue with apps that use nextcloud as a storage backend silently failing. Running on FairPhone 5 with F-Droid version of NextCloud App, version 34.0.1
FredL69 commentedon Jul 26, 2026
On my end, the 34.1.0 release seems to have fixed the problem.
alperozturk96 commentedon Aug 4, 2026
fixed via: #17270