iPhone is getting to hot - probably since update

Master_X · July 14, 2025, 7:09pm

Hey I already did several uploads of my whole photo library with the nextcloud app in iOS. I am using an iPhone 14 pro. Since the last 2 updates something broke the auto upload which is why I deleted everything once again and started from new.

Now something strange happened with the latest 2 versions 7.0.1 and 7.0.2. Maybe even the 7.0.0 update - I am not sure because I had no photos to sync between 7.0.0 and 7.0.1.

So as I said I completely reset and deleted the nextcloud app and reinstalled it. Then I went to auto upload and set everything as usual. First of all it creates something and demands the phone to be held active - don’t remember at the moment how it was called.
As soon it’s ready to upload and the transfer list can be opened the whole app gets slow and unresponsive. One time it even crashed after some minutes (not even starting uploading) but after opening again it was starting to upload. In transfer list it only said “uploading” but nothing starts. So this time I closed and restarted the app (like crashing) and they also started.

Now for the weird part. I always have the phone on a wireless charger and keep the display active as long it’s uploading. So sure it can get a bit warm. But as of now the phone gets incredible hot as far as it probably thermal throttles. So the already unresponsive nextcloud app is even more unresponsive and nearly not usable and uploads take ages. I am talking about around 1 photo per minute. Also the charger can’t keep the phone charged because it discharges faster and at one point it stops charging at all because it’s to hot.

It really seems to be a problem with the nextcloud app on iOS as far I can tell.

If there is anything more I can do to help just tell me. I don’t think the server setup matters but I am running a Kubuntu 24 OS with docker engine for several containers including docker-aio. Everything was working flawless until (I guess) the app got updated.

edit : and well I kept the phone off the charger and enabled power saving. After around 30 mins the app hangs and won’t do anything anymore.

edit : it took about 1 hour to drain my phone from 80% to 0
Am I really the only one with it?

tflidd · July 16, 2025, 7:22pm

If you go to the battery settings of your iphone, it should show the different app activity and how they contributed to the battery drainage.

It might be the iOS app (they changed quite some things in 7.0.0 especially for the sync process), or it might be the server, so the app is trying to upload over and over again. Then it can help to try with other interfaces/apps to upload larger amounts if you see problems there as well. And of course the logfiles.

I have just seen that you have also put a bug report on github:

github.com/nextcloud/ios

Unresponsive - battery drain - failing auto upload

opened 09:28AM - 16 Jul 25 UTC

Master1X

bug

### How to use GitHub * Please use the 👍 [reaction](https://blog.github.com/201…6-03-10-add-reactions-to-pull-requests-issues-and-comments/) to show that you are affected by the same issue. * Please don't comment if you have no relevant information to add. It's just extra noise for everyone subscribed to this issue. * Subscribe to receive notifications on status change and new comments. --- ### Steps to reproduce (probably) Initially my auto upload did not work anymore. Thats why I reset/redownloaded the app and bagan a new sync. 1. Download latest iOS app (I guess version 7 is culprit) 2. Start auto upload whole library with many files (photos and videos) 3. Wait until app is very unresponsive and phone is very hot and errors occur I can add logs from iOS and Kubuntu server if I know what to look for. Theres so much in it. ### Expected behaviour No errors, no burning phone, no unresponsive app ### Actual behaviour 423 WebDAV and incomplete upload errors occur and phone (14 pro) gets very hot (battery will drain 80% to 0% in about an hour). Keeping it on a charger causes overheat and it stops charging and probably throttles performance aswell. App crashes as well from time to time and is totally unresponsive. Sometimes is takes 30 seconds until my input registers. <img src="https://github.com/user-attachments/assets/c5ffa98b-56aa-449f-ae46-32ce403bbb3c" width="340" height="650" /> ### Reasoning or why should it be changed/implemented? It worked fine before and it's a no brainer the app should work properly ### Environment data **iOS version:** 18.5 **Nextcloud iOS app version:** 7.0.1 - 7.0.2.8 - 7.0.3.0 **Server operating system:** Kubuntu 24.04 **Web server:** Apache (Nextcloud AIO v11.3.0 docker engine) **Database:** Version: PostgreSQL 17.5 on x86_64-pc-linux-musl, compiled by gcc (Alpine 14.2.0) 14.2.0, 64-bit (Nextcloud AIO v11.3.0 docker engine) **PHP version:** Version: 8.3.22 (Nextcloud AIO v11.3.0 docker engine) **Nextcloud version:** [Nextcloud Hub 10](https://nextcloud.com/) (31.0.6)

Master_X · July 16, 2025, 11:58pm

It’s definitely only the nextcloud app draining the battery and yeah the 7.0 is pretty much what caused all of this. Also I checked the bettery tab already. I don’t think theres something trying uploading over and over again. I think there is something broken with the auto upload feature. Since it was all great until around first of the month it cannot be my server but who knows.

If you know what I could send from the logfiles just tell me. I don’t think it’s much useful to upload the whole thing.

tflidd · July 17, 2025, 12:17pm

You can set log levels in the settings of the app and also retrieve the logfile. I don’t know if your problem like this is obvious enough for the developers or not.

Just the locking problem often occurs when the fast redis locking cache is not used and the clients do very quick uploads. If they improved the upload performance of the ios-app, this might trigger now a problem and it was not fast enough before…

Master_X · July 17, 2025, 5:07pm

Oh yeah and completely forgot to mention the WebDav Error/File will be on the server if the error occurs. So what you said could make much sense.

Right now I am trying one more sync and and upload the log if neccessary

edit: it seems the root problem is fixed in the last version but the phone still gets very hot and battery drains fast. Over 10% in less than 30min. I cannot sync my whole library like that. Phone will be dead before finished

one more edit: phone still overheats and slows down but errors seem to be gone

edit again: app is now completely unresponsive again, maybe crashes soon or later and some larger (1GB) uploads failed again. Heres the log around one of these files with name 18-10-08 23-12-31 1946.mp4

2025-07-17 19:43:35 [INFO] Network response request: https://nextcloud.trolo.ddnss.de/index.php/core/preview?fileId=&x=1024&y=1024&a=1&mode=cover&forceIcon=0&mimeFallback=0&etag=9D9ADBBD-7E13-4DD2-B87F-6A107F8428EA, result: failure(Alamofire.AFError.responseValidationFailed(reason: Alamofire.AFError.ResponseValidationFailureReason.unacceptableStatusCode(code: 404)))
2025-07-17 19:43:36 [SUCCESS] Uploaded file: https://nextcloud.trolo.ddnss.de/remote.php/dav/files/master/Photos/2018/18-10-08 22-12-34 c7db.jpg, (290253 bytes)
2025-07-17 19:43:37 [DEBUG]  Upload file 18-10-08 23-12-31 1946.mp4 with Identifier F73978B9-D15E-4D27-A729-A951DCDAB100/L0/001 with size 298519913 [CHUNK 100000000, E2EE false]
2025-07-17 19:43:37 [INFO] Request started: PROPFIND https://nextcloud.trolo.ddnss.de/remote.php/dav/uploads/master/319BA9AB-1140-4B84-8F8B-CB169DCF138E
2025-07-17 19:43:38 [INFO] Network response request: https://nextcloud.trolo.ddnss.de/remote.php/dav/uploads/master/319BA9AB-1140-4B84-8F8B-CB169DCF138E, result: failure(Alamofire.AFError.responseValidationFailed(reason: Alamofire.AFError.ResponseValidationFailureReason.unacceptableStatusCode(code: 404)))
2025-07-17 19:43:38 [INFO] Request started: MKCOL https://nextcloud.trolo.ddnss.de/remote.php/dav/uploads/master/319BA9AB-1140-4B84-8F8B-CB169DCF138E
2025-07-17 19:43:38 [INFO] Network response request: https://nextcloud.trolo.ddnss.de/remote.php/dav/uploads/master/319BA9AB-1140-4B84-8F8B-CB169DCF138E, result: failure(Alamofire.AFError.responseSerializationFailed(reason: Alamofire.AFError.ResponseSerializationFailureReason.inputDataNilOrZeroLength))
2025-07-17 19:43:39 [INFO] Request started: No request created yet.
2025-07-17 19:43:40 [INFO] Request started: GET https://nextcloud.trolo.ddnss.de/index.php/core/preview?fileId=&x=1024&y=1024&a=1&mode=cover&forceIcon=0&mimeFallback=0&etag=E3F8685B-8716-4804-A618-561D5BDF1C5A
2025-07-17 19:43:40 [INFO] Request started: GET https://nextcloud.trolo.ddnss.de/index.php/core/preview?fileId=&x=1024&y=1024&a=1&mode=cover&forceIcon=0&mimeFallback=0&etag=E986FAB2-8786-4849-A370-BF7BCE90C255
2025-07-17 19:43:40 [INFO] Request started: GET https://nextcloud.trolo.ddnss.de/index.php/core/preview?fileId=&x=1024&y=1024&a=1&mode=cover&forceIcon=0&mimeFallback=0&etag=105E3C63-BCD3-47A8-A9A7-260FA4F17E4F
2025-07-17 19:43:40 [INFO] Request started: GET https://nextcloud.trolo.ddnss.de/index.php/core/preview?fileId=&x=1024&y=1024&a=1&mode=cover&forceIcon=0&mimeFallback=0&etag=358A7738-A9E3-4CCA-8DAF-6293EE74906D
2025-07-17 19:43:40 [INFO] Request started: No request created yet.
2025-07-17 19:43:40 [INFO] Request started: GET https://nextcloud.trolo.ddnss.de/index.php/core/preview?fileId=&x=1024&y=1024&a=1&mode=cover&forceIcon=0&mimeFallback=0&etag=D03F9249-A53C-4057-A417-00011FC7282B
2025-07-17 19:43:40 [INFO] Request started: GET https://nextcloud.trolo.ddnss.de/index.php/core/preview?fileId=&x=1024&y=1024&a=1&mode=cover&forceIcon=0&mimeFallback=0&etag=082CE7B8-CE20-4B53-ACDC-A208C26DA34D
2025-07-17 19:43:40 [INFO] Network response request: https://nextcloud.trolo.ddnss.de/index.php/core/preview?fileId=&x=1024&y=1024&a=1&mode=cover&forceIcon=0&mimeFallback=0&etag=D03F9249-A53C-4057-A417-00011FC7282B, result: failure(Alamofire.AFError.responseValidationFailed(reason: Alamofire.AFError.ResponseValidationFailureReason.unacceptableStatusCode(code: 404)))
2025-07-17 19:43:40 [INFO] Network response request: https://nextcloud.trolo.ddnss.de/index.php/core/preview?fileId=&x=1024&y=1024&a=1&mode=cover&forceIcon=0&mimeFallback=0&etag=105E3C63-BCD3-47A8-A9A7-260FA4F17E4F, result: failure(Alamofire.AFError.responseValidationFailed(reason: Alamofire.AFError.ResponseValidationFailureReason.unacceptableStatusCode(code: 404)))
2025-07-17 19:43:40 [INFO] Network response request: https://nextcloud.trolo.ddnss.de/index.php/core/preview?fileId=&x=1024&y=1024&a=1&mode=cover&forceIcon=0&mimeFallback=0&etag=E3F8685B-8716-4804-A618-561D5BDF1C5A, result: failure(Alamofire.AFError.responseValidationFailed(reason: Alamofire.AFError.ResponseValidationFailureReason.unacceptableStatusCode(code: 404)))
2025-07-17 19:43:40 [INFO] Network response request: https://nextcloud.trolo.ddnss.de/index.php/core/preview?fileId=&x=1024&y=1024&a=1&mode=cover&forceIcon=0&mimeFallback=0&etag=358A7738-A9E3-4CCA-8DAF-6293EE74906D, result: failure(Alamofire.AFError.responseValidationFailed(reason: Alamofire.AFError.ResponseValidationFailureReason.unacceptableStatusCode(code: 404)))
2025-07-17 19:43:40 [INFO] Network response request: https://nextcloud.trolo.ddnss.de/index.php/core/preview?fileId=&x=1024&y=1024&a=1&mode=cover&forceIcon=0&mimeFallback=0&etag=CCFCCA6E-2278-42A6-94A8-331CD358A413, result: failure(Alamofire.AFError.responseValidationFailed(reason: Alamofire.AFError.ResponseValidationFailureReason.unacceptableStatusCode(code: 404)))
2025-07-17 19:43:41 [INFO] Network response request: https://nextcloud.trolo.ddnss.de/remote.php/dav/uploads/master/319BA9AB-1140-4B84-8F8B-CB169DCF138E/1, result: failure(Alamofire.AFError.responseSerializationFailed(reason: Alamofire.AFError.ResponseSerializationFailureReason.inputDataNilOrZeroLength))
2025-07-17 19:43:41 [ERROR] Upload incomplete: only 100000000 bytes sent.
2025-07-17 19:43:41 [ERROR] Upload file: https://nextcloud.trolo.ddnss.de/remote.php/dav/files/master/Photos/2018/18-10-08 23-12-31 1946.mp4, result: error -9993
2025-07-17 19:43:43 [DEBUG] PROCESS (UPLOAD) find 8 items
2025-07-17 19:43:43 [INFO] Request started: GET https://nextcloud.trolo.ddnss.de/index.php/core/preview?fileId=&x=1024&y=1024&a=1&mode=cover&forceIcon=0&mimeFallback=0&etag=E3F8685B-8716-4804-A618-561D5BDF1C5A
2025-07-17 19:43:43 [INFO] Request started: GET

tflidd · July 18, 2025, 8:55am

If you see this more often, with problems of chunked uploads, there might be more topics about that, especially if you use reverse proxies.

Master_X · July 18, 2025, 9:59am

github.com/nextcloud/docker

Apache images built after ~mid June 2022 introduce 1GB upload limit

opened 08:58AM - 28 Jul 22 UTC

closed 07:29PM - 21 Oct 23 UTC

henryk

bug upstream

After my last docker image update I suddenly saw upload failures for very large …files, even though I hadn't changed any configuration, and the nextcloud docker build also has no related configuration changes. I finally tracked the problem down to a change in Apache default configuration. Steps to reproduce: 1. Start with nextcloud apache docker image built before June 9, 2022 2. Check included Apache version (is 2.4.53) 3. Create large testfile (`dd if=/dev/zero of=testfile bs=1M count=1025`) 4. Create upload share in nextcloud 5. `curl -X PUT -H "X-Requested-With: XMLHttpRequest" -T testfile http://<shareid>:<sharepass>@<host>/public.php/webdav/testfile` 6. Update docker image to newest version (Apache is now 2.4.54) 7. `curl -X PUT -H "X-Requested-With: XMLHttpRequest" -T testfile http://<shareid>:<sharepass>@<host>/public.php/webdav/testfile2` Actual result: Step 5 works, Step 7 doesn't work. A smaller testfile (`dd if=/dev/zero of=testfile bs=1M count=1024`) will still work with the new image. Root cause: https://httpd.apache.org/docs/current/en/mod/core.html#limitrequestbody has changed default value in Apache version 2.4.53 from 0 (unlimited) to 1073741824. Note: This also means the the various documentation entries about increasing PHP_UPLOAD_LIMIT etc. don't apply. IMHO this is a regression, and the apache nextcloud docker image should change the builtin Apache configuration back to the old value of 0 (unlimited).

this is what I found so far

tflidd · July 18, 2025, 11:36am

But yours is 100 MB.

Master_X · July 18, 2025, 11:54am

Yeah maybe it was really the not set limit by caddy? But I wonder why this was no problem or at least why I did not notice this before .

I now added this to the caddyfile

reverse_proxy http://nextcloud-aio-apache:11000
}
request_body {
    max_size 50GB
}

and added these enviroment vars

  NEXTCLOUD_MEMORY_LIMIT: "1024M"
  NEXTCLOUD_UPLOAD_LIMIT: "50G"
  APACHE_BODY_LIMIT: "0"

Do you know if APACHE_BODY_LIMIT works in docker-aio ? Found no clear documentation about this