Repository navigation
feature: auto upload #16678
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
Take1)
- Take Android 11 (Samsung A40)
- Create some photoes
- Create some screenshots
- install the APK provided here [https://cloud.nextcloud.com/s/CBsW4ST38LQ8gCP] ( Auto-upload: Call for debug help #16550 )
- accept akku not-optimized and full access for the client
- Activate sync of the two default provided folders (Camera and Screenshots).
- The folders did not exist on the server yet (i was used to they just get created).
- disable wifi only.
- enable existing files
- enable use subfolders yyyy/mm
- eneable "new version renaming"
Take2)
- disable the default synch (screenshots and camera)
- create custom synch orders
- one for Camera one for Screenshots
- create both target folders on nextcloud manually
- all other settings as above
- start sync
Expected behaviour
the existing files get synched. New taken pictues are synched.
Actual behaviour
take 1) Nothing was synched at all. Not even the folders created. (logs_0.txt)
take 2) Only new pictures get synched. Existing ignored (logs_1.txt / logs_1b.txt). Log 1b is after the sync happened. i thought it would not happen anymore. but actually it came a bit later.
Android version
11
Device brand and model
Samsung A40
Stock or custom OS?
Stock
Nextcloud android app version
Custom from #16550
Nextcloud server version
version 32.0.5 (Self hosted locally)
Using a reverse proxy?
No
Android logs
Server error logs
I think i covered those in some settings yet. As far i understood they are not harmful anymore. But for the sake of completenes i post that here.
Fehler
core
Exception
HMAC does not match.
15.03.2026, 12:45:36
Fehler
core
TransportException
Connection could not be established with host "127.0.0.1:25": stream_socket_client(): Unable to connect to 127.0.0.1:25 (Connection refused)
15.03.2026, 12:39:15
Fatal
core
Request used more than 300 MB of RAM: 1.1 GB
15.03.2026, 11:56:41
Warnung
cron
Cron job used more than 300 MB of ram after executing job OCA\Recognize\BackgroundJobs\ClusterFacesJob (id: 9259, arguments: {"userId":"Axel"}): 1.1 GB (before: 26.7 MB)
15.03.2026, 11:56:24
Fatal
core
Request used more than 300 MB of RAM: 1.2 GB
15.03.2026, 11:49:52
Warnung
cron
Cron job used more than 300 MB of ram after executing job OCA\Recognize\BackgroundJobs\ClusterFacesJob (id: 9256, arguments: {"userId":"Axel"}): 1.2 GB (before: 104.3 MB)
15.03.2026, 11:49:52
Fatal
core
Request used more than 300 MB of RAM: 1.1 GB
15.03.2026, 11:21:25
Warnung
cron
Cron job used more than 300 MB of ram after executing job OCA\Recognize\BackgroundJobs\ClusterFacesJob (id: 8927, arguments: {"userId":"Axel"}): 1.1 GB (before: 28.1 MB)
15.03.2026, 11:21:25
Fatal
core
Request used more than 300 MB of RAM: 1.1 GBAdditional information
This issue is related to
#16550 (call for debug help)
Activity
AxelPanningDE commentedon Mar 15, 2026
logs_1b.txt
forgot logs_1b.txt
alperozturk96 commentedon Mar 16, 2026
Hey, thanks for the feedback.
For the scenario 1, you just pressed the cloud icon right? Because when I checked the logs I saw
No enabled synced folders found — skipping file sync.Which is not expected I just tried same scenario and immediately detected the folder. Could you please confirm?AxelPanningDE commentedon Mar 16, 2026
No, i opened the menu via the 3 dots. In there i also toggled the active swipe on top.
Then i changed some settings:
-disable wifi only.
-enable existing files
-enable use subfolders yyyy/mm
-eneable "new version renaming
edit: fyi, when i connected initially i had some typos in the server connection ip. so there were 3-4 tries to connect the server at all. not sure how this is represented in the logs
alperozturk96 commentedon Sep 14, 2026
Hey,
Could you please try to reproduce the issue described in the first message using 35.0.0 RC2 and let us know whether the issue has been resolved?
To help us keep things organized and make sure we can track each issue properly, please keep this discussion focused on the issue described in the original report.
If you notice a different issue, have a separate feature request, or would like to discuss another improvement, please create a separate issue for it. This will help us investigate and track each topic individually.
Thank you for your help and feedback! 🙌