I have problems with uploading “large” files (larger than 20 MB) using the Android app for some time now. I can upload files up to 2 GB via the iOS app and the browser but not via the Android App. Why? Can anyone help me with this?
Is there a way to set the chunksize and chunktimeout in the android app as a workaround? @Andy do you have an idea?
You need to provide more information. There is a support template here on the forum that requests additional information for a reason. We can’t help you if you don’t give us what’s needed to help you.
What version of Nextcloud Server? What version of the Android client?
What, precisely, happens when you upload larger files?
What appears in your Nextcloud log during these failed transactions?
Are you using a reverse proxy and/or something like CloudFlare?
What version of Nextcloud Server? 29.0.2
What version of the Android client? 3.29.0
What appears in your Nextcloud log during these failed transactions?
When I try to upload a file with 500 MB, the Nextcloud app uploads the file up to 7%. I tried to upload the file 5 times. Each time the upload stops at 7%. I see the following entry in the server log:
BadRequest Expected filesize of 40960000 bytes but read (from Nextcloud client) and wrote (to Nextcloud storage) 30470144 bytes. Could either be a network problem on the sending side or a problem writing to the storage on the server side.
What I see is the error message of the Nextcloud app:
There is no way to influence the chunk size or time-outs. So I would suggest to raise a ticket in the issue tracker and mention some of the devs like Tobias or Alper.
Doesn’t sound like a server issue given your statement that it works on the iOS app.
Today I tested the same file with a hosted Nextcloud instance (opsone, CH). The strange thing is that I can upload the 520MB file to Nextcloud. Maybe it’s a server problem. But I have changed all necessary values as in php.ini to 2GB. But why can I upload big files with the iOS App. Is the upload behaviour of the iOS app different to the android one? Do you have an answer for this problem?
sorry for the late reply. I can’t tell why it works for iOS, might be worth raising in a ticket on Github since I do not know the specifics of either implementation on a detailed level to guess why the behavior is different.