Repository navigation
Insufficient space to copy files when "keep files in source folder" is selected. #5592
Description
Steps to reproduce
- Open the Nextcloud Android app
- Choose file(s) to upload, that in total are greater in size than the remaining free space on the device
- Select "Keep file in source folder"
- Tap upload
Expected behaviour
Because I have selected to keep the files in the source folder, it should not matter that I have selected, for example, 2GB of files, when I have 1GB of free space on my device.
Actual behaviour
The app displays an alert that there is insufficient space to copy the files to the Nextcloud folder, and asks if you would like to move the files instead of copying them
Environment data
Android version: Android 10, security patch level 6 October 2019
Device model: Google Pixel
Stock or customized system: stock, un-rooted Android.
Nextcloud app version: 3.10.1
Nextcloud server version: 18.0.1
Logs
Web server error log
N/A
Nextcloud log (data/nextcloud.log)
N/A
Issue #4465 is pretty much identical, but was closed due to been inactive for a month, without receiving an answer.
If this is a setting that I need to change in the app or on the server side, then please let me know. Any help will be appreciated. Thanks.
Activity
AndyScherzinger commentedon Mar 10, 2020
cc @tobiasKaminsky for feedback
@The1ComputerGuy to provide some info/context about this behavior, for uploads the files are actually copy to an internal directory and get deleted after a successful upload.
AlexVerrico commentedon Mar 16, 2020
Hi @AndyScherzinger
Thanks for clarifying that.
Perhaps then a feature request would be for the app to follow this workflow:
Copy one file -> Upload one file -> Delete temporary file.
Instead of what I assume it is doing currently:
Copy all files -> Upload all files -> Delete all temporary files.
Cheers.
AndyScherzinger commentedon Mar 16, 2020
@tobiasKaminsky can you on @AlexVerrico's assessment? I guess he is right with how it works today while I haven't had the time to check the code.
tobiasKaminsky commentedon Mar 21, 2020
Yeah, we have to look into this logic again…
leonhandreke commentedon Jan 19, 2021
FWIW, this is also happening to me with plenty of free space to copy the files. I'm on LineageOS 17. Please let me know if you need more info.
panomitrius commentedon Apr 16, 2021
I have a 50gb+ photo library which can't get uploaded because Android nextcloud client wants to copy them somewhere first. I don't get anywhere since I don't have another 50gb space free. Why isn't there an option to just upload, without any copying around on the phone?
peoplenamed commentedon Dec 25, 2021
Is the copy action needed? This issue is still present.
AlvaroBrey commentedon Jun 16, 2022
Currently, as much space as the files you trying to upload occupy.
@tobiasKaminsky @AndyScherzinger what is the reason behind copying before upload? Perhaps it can be avoided altogether
AndyScherzinger commentedon Sep 26, 2022
@tobiasKaminsky might remember but I would guess to ensure the files hasn't been touched or is changing while you upload it, since there is no locking of the local file
hakunamatata97k commentedon Feb 26, 2023
@AndyScherzinger While this is a valid answer. It doesn't apply on usages where periodic backup is utilized using the app!.
Backing up a wapping 210Gb of data from my 250Gb phone on to my server, proves to be an impossible task!.
Chunking up would make less sense as well :(
Plus assuming I have smaller 60Gb media folders "moving to nextcloud folder" would disrupt the larger file structure! Especially when working with editing videos and images :/
Please provide your take on the subject. :)
flo-kei commentedon Dec 1, 2023
Is there any plan on improving the current situation? The current implementation is not very usable.
arf20 commentedon Apr 4, 2024
I second this. The whole point of getting the android app was to backup my photos to my nextcloud instance, it was only when I tried to upload them that I was greeted with this error message.
I think this "duplicating everything and uploading the copy" is bad and useless. It requires the uploader to have double the space available of the thing trying to be uploaded. In most cases, pictures. In most cases, pictures take the majority of space in a phone. So this is against the expected use case of the feature.
Also useless because in the time nextcloud finishes copying everything, files could have been changed in the process.
Wyzski commentedon May 17, 2024
I am experiencing the same issue described here, any updates or workarounds?
LevAnni777 commentedon Jul 14, 2024
I can't believe this problem still exists. Why don't just simply upload the file directly to the server instead of copying it to some temporary directory first?
MoritzLange commentedon Sep 7, 2024
I think a possible workaround, if you want to upload the entire content of one folder (e.g. camera images) to the server, is auto upload. In the app (at least my current Android app) you can go to 'Settings' -> 'Auto upload' and select a folder. Click the ⋮symbol and then 'Configure' to get to a menu where you can specify a remote folder to sync with. In the same menu you can also select whether to upload existing files or only new files.
jjmacid commentedon Nov 6, 2025
Hello, can anyone update on this issue, because it's impossible that after 5 years it still exists. Can you clarify:
1/ Is it a problem that will always exist because of Google Play blocking something and we must download the F-Droid version or this problem occurs also in the F-Droid version? (Note: Does Google Play force to check the source code? If so, Businesses that publish their commercial apps must show their code?)
2/ Is it a security problem when copying files from DCIM folders that prevent NextCloud to delete the original local file in that DCIM folder? If so, why Nextcloud creates a local copy of the files? It doesn't make any sense to duplicate the file and then delete the duplicate when "Move file to the server" is requested. But, anyway, the problem is that it didn't even delete the duplicate.
So please clarify if possible the situation, cause I think there are too many unanswered Issues that point to the same question.