Cannot upload large files
Thanks a lot for the great app! We discovered a problem uploading large files via the Nextcloud app:
Steps to reproduce
- Open Nextcloud app (iphone, ipad)
- Enable Chunking in settings to 10 MB
- Upload 2GB file
Expected behaviour
- Upload starts
Actual behaviour
Error Message "Could not read the file" (read_file_error)
Tested on ipad and iphone with two nextcloud installations, installed by different admins.
BUT: If I copy the file within the Apple "Files" Application to the Nextcloud-Location it is working. It's also working with small files (so it seems to be no permission problem). It's also working from Android app. It's also working using Safari.
Logs
No log output in app even with highest log level
Reasoning or why should it be changed/implemented?
Seems to be a bug
Environment data
iOS 14.4.2 (ipad) iOS 14.6 (iphone)
Nextcloud iOS app version: see More > Settings
4.0.5.8
Server operating system:
Ubuntu 20.04.2 LTS
Web server: Apache, nginx
nginx 1.18.0
Database:
MariaDB 10.3.30
PHP version:
7.4.3
Nextcloud version: see Nextcloud admin page
21.0.3 19.x 20.x
If we can contribute with any further information we are glad to assist, also we can do debugging server-side. In our eyes it seems to be a problem with the application (though uploading large files with the mobile application seems to be not the most common use case ;) We also found #221 but it's not clear if it's a related problem.
Hi, where do you get the file from ? (camera roll) ?
Hi and thanks for getting back on this,
the file comes from "files" (Upload file, second option after touching the + sign) and is stored on the iphone/ipad. I've tested with files I fetched with the nextcloud-app and moved to the store of the ios-devices as well as with files I got via airdrop to the ios-devices. Smaller files (I've tested a 20 MB-file are working). I have tested with several devices, colleagues will do further testings tomorrow. If we get any new insights we will update the issue.
Hi, is there any update on this. I saw the PR for this issue. In the current version 4.3.1.0 the issue is still present.