Auto-upload on android not uploading anything

Not sure. Is that folder enabled for uploading and set up the same as the one with the photos?

lol yes sure. its just custom made, the photos are recognized by the app itself, the other folder I chose myself and directed it to a folder in the cloud. some stuff was uploaded (see above) but like half is not…, new stuff apperently also not… when I am at home I will make a new, empty folder, sync it, and copy everything I want backuped into it piece by piece. maybe that will change something…

@edit: did not. just some random folder was uploaded, nothing else. but the audiobook i added this morning was miraculously uploaded in the late evening. activity tab showed: -FileXY changed at 8am ; FileXY created at 10pm (that was when it was upladed, even though i was in wifi for hours).
weird weird…

I have nextcloud android version 3.32.2 does not upload anything automatically… not the automatically created things, or the manually created sync things… Nothing in the log, on the server as well… :expressionless_face: :exploding_head:

Well, for me it uploads most images, but not all of them. It is simply unreliable. So I guess I need to implement some occasional checks to see if everything is in sync? It is also a bit annoying, as many times, one wants to take a picture, and then quickly use it on the computer… most of the times it works, sometimes not. 3.32.2

This is likely caused by a decision of Google to revoke required permissions:

Personally I use FolderSync instead which works quite well so far and also has an automatic upload function for new images from the camera - but FolderSync is not open source and depending on what you want to use, you may have to purchase the “Pro” version.

On your Samsung S10 with Nextcloud Android app version 3.13.0, the auto-upload feature isn’t working—you’re unable to upload both old and new photos.

Foldersync is an awesome interim suggestion

Starting with Android app 3.2x ist seems, that the app sometimes does its own “brain”:
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.

The problem with photo auto upload on the Android app still exists. I have a Pixel 7a and for several app versions now, auto upload photos has been completely unusable. It seems others are experiencing the same issue. I hope this core feature will be restored soon.

https://github.com/nextcloud/android/issues/16334

I don’t know if it has been mentioned in this thread, but I was having problems with auto upload on Android and I found an app called FolderSync (and no, I have no affiliation with them, just a user). It works great. You do need to use an app password to connect, but I have been using it now for months and it just works. I used the free version for a while, but eventually bought the app (it was cheap) since it worked well. I think the free version limited filters (IE: only upload jpg and png, etc) and maybe there were ads? I don’t remember for sure.

EDIT: lol…3 posts up it was mentioned.

This thread is years old and the summary is still basically “yeah it’s unreliable, use FolderSync.” I made an app called Photos Copy — WebDAV photo backup for Android where you can actually see what’s copied, what’s waiting and what failed. photoscopy.pages.dev.

Since this still comes up: before switching apps, check Android’s background restrictions for Nextcloud—set battery usage to Unrestricted, allow background data, and turn off any “pause app activity if unused” setting. Also verify the auto-upload target folder exists on the server; failed uploads often show a different path than the auto-upload setting, as Mornsgrans noted. If uploads only work while the app is open, that usually points to Android killing the sync process rather than a server-side failure.