Auto Upload of Photos Not Working Since Nextcloud Android App v3

Since updating to Nextcloud Android App version 3.32, the automatic upload of photos to my Nextcloud server has stopped working. In the previous version, everything worked flawlessly.

I tested this issue on two devices: Moto G53 (Android 13) and Moto G85 (Android 15), both running Android. The problem occurs on both devices.

Please advise if there is a known issue or a workaround for this.
Server Nextcloud ver. [Nextcloud Hub 10] (31.0.6)
Thank you.

Hi, I just learned in this topic (Nextcloud Android App Version 3.32 - Automatischer Fotoupload "Lokale Datei nicht gefunden" / Auto Upload: Local File not found - #4 by maziarz189) that there is another setting you have to set. It is not enough to set access to “all photos” in the access tab of the Nextcloud app. You also need to register the Nextcloud app in this menu :

Settings > Apps > Special app access > All files access

Tested and automatic upload works (again) on Moto G75 and G54.
I was not aware of this setting until today… (when Maziarz189 hinted me that way!)

1 Like

Also does not work for me with normal uploads.

Just noticed mine aren’t updating either for days.

Enabled Special App Access and will monitor.

After setting up full access, the photos sync but only the new ones, not the older ones.

1 Like

Hi I have the same problem with an up-to-date Samsung S21 and Nextcloud app 3.32.2. But, with my other smartphone under /e/OS (Degoogled Android 12) everything works wilt the same Nextcloud app.
Did you find a solution?

I have the same problem, Motorola G84 mobile phone, Android 15, and Nextcloud 3.32.2. I have set the access rights and the battery as well.

So far, I have solved this by installing the developer version DEV 20250822.

Same problem on both Samsung Galaxy A52s 5G and Google Pixel 9a, Netxcloud app 3.32.3 from Playstore: only some random photos are uploading. I can reinstall the app, give battery permission, but upload only works for 1 or 2 photos, then it stop working. Maybe one photo will be uploaded in the next days.
Is there a way to force a rescan and reupload of all missing (not uploaded) images ?

1 Like

Adding to this one, I’m a long time nextcloud user it’s awesome, and mostly these android imposed permission updates seem to go away easily enough following community advice, but september has not been succesful for me: clear cache, uninstall app, reinstall for permissions and reconfigure uploads, reboots after each change etc.

Android app v3.34.0
Samsung S20FE
Nextcloud Hub 10 (31.0.9) on Ubuntu

temporarily using foldersync app to get files copied on a schedule

My only quirk is camera defaults to SDcard, but even when changing to internal storage (and selecting auto upload for just one folder) if i open nextcloud app, then switch to camera and take a snap and then come back to nextcloud, in the “uploads” section it says no uploads available. as others have mentioned, a manual upload works fine within the app, it’s just the nextcloud app doesn’t “see” there is a new file. It can see the new pic in the folder thumbnails when selecting which folder to upload, but just doesnt recognise it as a new one to upload

I did install Android app version 3.30.8 from F-Droid, so the app will not be overwritten by Google Play.

The 3.x app versions all seem not work properly:

  1. delay up to more than 15 minutes to start the auto upload
  2. the app sometimes changes the upload folder from /camera/year/month to /camera/year/month/storage/emulated/0/dcim/Camera (if additional folders do not exist, the upload fails), see target folder of failed uploads in “Uploads” - in the auto upload settinge still /camera/year/month is set. Create the additional foldertree (/storage/emulated/0/dcim/Camera) on the server, restart the uploads and do a reboot of your Android device after upload.

quick update to let folks know this is now resolved.

I updated container to 32.0.0 and suddenly I had 6000+ images to sync up. I cancelled the uploads (all pre-existing) and now i have instant upload working again; so it must have been a glitch with the docker image 31.0.9

Good luck everyone :slight_smile:

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.