Andoid App is not syncing at all

vty · September 18, 2025, 12:03pm

Hi,

I’m new to NextCloud, loving the features!

I set up a server and it’s successfully syncing from my Windows OS. But whatever I do I can’t get the ‘Auto-Upload’ / Sync to work with Android.

What I’ve tried:

I’ve installed various versions 3.33.0 (Play Store), 3.33.0RC2 (F-Droid), 3.34.0RC1 (Play Store)
Set “access to all files” and allowed “access to photos”
Remove all battery restrictions
Restarted the phone
Remove and re-added all syncs
Add Manual Sync folder (instead of the suggested photo folders)
Enable/Disable two-way-sync

The only thing that seems to work is manual uploading some files.

The folder Icons so show the ‘Auto Upload’ icon (arrow pointing upwards).

I’m at a loss.. What else can I try here?

vty · September 18, 2025, 12:05pm

Would like to highlight that I’ve read this:

..however that doesn’t seem to be my issue since no files (photo or otherwise) are synced at all, while manual upload does work.

vty · September 19, 2025, 12:49pm

I think perhaps my issue is related to this:

github.com/nextcloud/android

Automatic Upload only works with default Folders (Android 16)

opened 07:18AM - 01 Aug 25 UTC

fsesterh

bug 0. Needs triage

### ⚠️ Before posting ⚠️ - [x] This is a **bug**, not a question or an enhancem…ent. - [x] I've [searched for similar issues](https://github.com/nextcloud/android/issues) and didn't find a duplicate. - [x] I've written a clear and descriptive title for this issue, not just "Bug" or "Crash". - [x] I agree to follow Nextcloud's [Code of Conduct](https://nextcloud.com/contribute/code-of-conduct/). ### Steps to reproduce 1. create a custom folder "photos" 2. set the camera path to sync photos to this folder RESULT: Nothing gets synced. - Nextcloud HAS full access to ALL files. - Manually Sharing a photo/file and selecting the folder configured for automatic sync works instantly! ### Expected behaviour This should work. ### Actual behaviour What seems to happen instead is that nextcloud wants to shove everything under SofortUpload/[App/Folder]. I.e. if you activate automatic upload for WhatsApp Images and you DO NOT change the path the App will create "./SofortUpload/WhatsApp Images" ! Then files are uploaded immediately ! Changing the path breaks uploads for WhatsApp images. Even worse, if you disable the sync and remove "./SofortUpload/WhatsApp Images" and then reactivate the sync nextcloud will not create the folder again. Manualle creating "./SofortUpload/WhatsApp Images" does not help. You cannot sync this stuff again, ever. ### Android version 16 ### Device brand and model Pixel 9 Pro ### Stock or custom OS? Stock ### Nextcloud android app version 3.32.2 ### Nextcloud server version 31.0.7 ### Using a reverse proxy? I don't know ### Android logs _No response_ ### Server error logs ```bash ``` ### Additional information _No response_

Even though I didn’t manage to get the app to sync, even after reinstalling it and using only the default folders.

Is anyone else having similar issues?

Spindoctor · November 8, 2025, 12:16pm

I do have the same issue on my Pixel 8

jvenable27 · December 30, 2025, 2:03am

To keep this going - YES, I am having the same issue over the last several days. I was using thegood.cloud as my server and recently switched to Felicloud and noticed that is when the sync issues began. Everything worked fine with thegood.cloud so I reached out to Felicloud and they stated that since I can manually upload files then the issue is with the Nextcloud Android app.

I am running the latest version - 3.34.1 (suggested version via F-Droid)

Also, my Seedvault backup seems to be coming through just fine, but that isn’t a sync type as that is pushed via DAVx5.

sylver · January 13, 2026, 8:00pm

Facing the same issue. I had NextCloud working well for a lot of years, but it seems like the Android app has lost the ability to automatically sync files from my phone to my server. I can manually upload them. But until I do, the app doesn’t seem to recognize that new photos or videos have been created on the phone. Is this all still related to the Google problem mentioned previously in the thread? Or, is there something I can do to pull logs from the client to troubleshoot the issue?