Upgrade to 3.20.x breaks auto upload (no longer detects new files and uploads)

[mepreston]

Steps to reproduce

1. have version 3.19.1 installed
2. upgrade to 3.20.0 or 3.20.1
3. auto upload no longer works

Expected behaviour

• this is a regression. autoupload should continue to work

Actual behaviour

• it no longer auto uploads any new pics

• Can you reproduce this problem on https://try.nextcloud.com?

  not uploading server logs as it doesn't even attempt to contact the server to upload.

Environment data

Android version: 10

Device model: moto g7 power

Stock or customized system:

Nextcloud app version: 3.20.x

Nextcloud server version: 23.0.4

Reverse proxy: no

workaround: downgraded to 3.19.1 and it is working fine again

[Foritus]

I am also experiencing this on my Xiaomi Redmi Note, as is my partner.

[manvis]

Same here. Took a lot of photos recently, but I've noticed that none of them reached the server.

[crycode-de]

Same here since last app update.

Android version: 10 Device model: Cubot X30 Nextcloud app version: 3.20.1 Nextcloud server version: 23.0.4

[dtrouillet]

Same here: Android version: 10 Device model: Honor 10 View Nextcloud app version: 3.20.1 Nextcloud server version: 23.0.3

[Mindstan]

Same issue (last time it did work according to the logs was the 17/04/2022): Android version: 10 Device Model: Samsung Galaxy S9 (Exynos variant) Nexcloud app version: 3.20.1 (excluded from power management) Nexcloud server version: 23.0.0

[AlvaroBrey]

I'll try to reproduce this. Has anyone verified if it happens in a fresh install of 3.20.0? (not upgrade)

[AlvaroBrey]

I wasn't able to reproduce this. Can anyone upload a logcat?

[xaavro]

Same here too. Since 3.20.x my auto-upload folders are not backing up new files to my server. At first I thought it was related to MIUI saving settings, but after checking everything, not even with the app opened works.

[mepreston]

if there was an existing logfile on the client i'd be happy to upload it but i'm not doing the adb thing to get you a log. i complained years ago when you first did away with logs on the client and was ignored.

[originalsouth]

I wasn't able to reproduce this. Can anyone upload a logcat?

See logcatOutput.txt (with redacted username/host/port/user-folders)

[AlvaroBrey]

I wasn't able to reproduce this. Can anyone upload a logcat?

See logcatOutput.txt (with redacted username/host/port/user-folders)

Thanks! From this and another log that was shared with me privately, unfortunately I see no obvious cause of the problem; it seems like the media scan is triggered but the upload is never even queued. We'll have to try harder to reproduce this.

[Wikinaut]

Same issue here.

• Server Nextcloud Nextcloud Hub II (23.0.4)
• Android App 3.20.1
• Android 10
• HUAWEI P smart 2019

[David-Lor]

Having this problem as well, but I was using an older version (tried upgrading to the 3.20.1 though, same problem). Upload was working perfectly fine. I think it may have stopped working after deleting all the pictures and videos I had on my phone (that's the only think related to the folders I have on auto-upload I've been doing recently). Now nothing of my auto-upload configured folders get uploaded. The settings are fine (auto-upload enabled and all the desired folders enabled and well configured, as always).

Edit: I uninstalled the app (which also removed all synced files and configuration from my device) and reinstalled again (latest version): auto upload working fine now again.

[MarcoMas6]

Hi, i had the same problem too...i tried to upgrade the server, make update of all android market, but without success. I can see the photo's folder, but auto upload doesn't work.

Some days ago, i received update of play store (i saw android web view and other android things) and now auto upload works again ! I don't know what happened !

[jkpirie]

Installed 3.20.1 tonight to try and fix the auto upload not working on 3.20. 3.20.1 does not find any media folders on my device! I can set up a custom folder linked to my camera save location and this uploads pictures taken automatically however I cannot differentiate between pictures and videos therefore they all end up in the same backup location. Perhaps this is 'new' intended behaviour? Anyway, I have reinstalled version 3.19.1 for now to see if the auto discovery of media folders will be reinstated? It was much more satisfactory as a modus operandi. James

[kevenwyld]

Having this issue as well. As a workaround creating a custom rule for that folder like @jkpirie suggested works but I can't differentiate between images and videos that way like the default rules. Before I was sending videos to a different directory in Nextcloud but they were in the same one on the mobile device.

The default auto upload rules seem to just do nothing after the to 3.20.x . I have not yet tried reinstalling the application but I think that shouldn't be necessary, especially considering that removes any app configuration and local data as well.

[kadrim]

same here, stopped working right after the upgrade to 3.20.0 on two of my devices

[InfamousUser]

Lucky you people, it hasn't worked for years for me.

[xaavro]

I got mine to work again. After granting the app permissions for accessing contacts and calendar it started uploading all the pending files. Berore that I had permissions enabled for camera and storage only.

[naudster]

Same problem for me on two devices, v 3.20.1. Enabling the contact and calendar permissions (which were disabled) as @xaavro suggested hasn't worked.

Note that in Settings -> Auto Upload, if I disable and re-enable a folder by hitting the cloud button, it prompts: "Your device may have battery optimisation enabled ...." . However this is false. I can confirm in the Android Battery Optimisation screen that the Nextcloud app is "Not optimised".

[originalsouth]

Note that in Settings -> Auto Upload, if I disable and re-enable a folder by hitting the cloud button, it prompts: "Your device may have battery optimisation enabled ...." . However this is false. I can confirm in the Android Battery Optimisation screen that the Nextcloud app is "Not optimised".

"Your device may have battery optimisation enabled ...."

[xaavro]

Little update on the issue. Disabling again camera and contact permissions didn't break the auto-upload. Maybe changing them the first time somehow "refreshed" all permissions and made the app to work again?

[ennyjr]

Same here: Android version: 10 Device model: Poco F1 Nextcloud app version: 3.20.1 Nextcloud server version: 24.0.0 Granted all permissions to the app, and turned off battery saver last automatic upload 03/05

[grey-liu]

same problem

I found some directory not appear in 'setting' - 'auto upload' page.

solve the problem 1: stop app, kill process. 2: disable 'storage' permission and enable again for nextcloud app in system permission setting page. 3: launch app, it start auto upload.

[ennyjr]

same problem

I found some directory not appear in 'setting' - 'auto upload' page.

solve the problem 1: stop app, kill process. 2: disable 'storage' permission and enable again for nextcloud app in system permission setting page. 3: launch app, it start auto upload.

Here it worked, thank you

[Mindstan]

Worked for me too, thanks!

[kadrim]

same problem

I found some directory not appear in 'setting' - 'auto upload' page.

solve the problem 1: stop app, kill process. 2: disable 'storage' permission and enable again for nextcloud app in system permission setting page. 3: launch app, it start auto upload.

worked for me!

but i had to do it this way:

1. kill/force-stop app
2. disable storage permission
3. launch app
4. add permission via bottom-bar within the nextcloud app

[manvis]

Worked for me as well. Looks like that completely stopping the app before attempting is a very important part of this fix because I'm almost sure I tried disabling and enabling permissions a few days ago and nothing happened. Thanks, @OrangeGeeker.

[kevenwyld]

I can confirm this worked for me as well. I did as @kadrim suggested and let the app request the permissions again after removing them.

[originalsouth]

So the solution proposed by @OrangeGeeker also works for me. The files that were not uploaded since the app broke, however, remain unuploaded -- new files are uploaded. Is there a way to have the app upload these files?

[kevenwyld]

@originalsouth when I did this it uploaded everything that had been ignored since it was broken. That ended up being hundreds of photos/videos with many conflicts as I had uploaded some of them manually.

I was aware that your situation was a possibility though and purposely did not try any of the other mitigation steps like reinstalling the app, etc, and was careful not to change the default auto-upload rules other than temporarily disabling them. It's possible if you reinstalled, cleared the cache, or similar, the android app lost it's list of pending items. You may need to select them and manually upload back to the original date that auto-upload stopped working.

I'm not an expert here though, this is just based on observations when troubleshooting auto-upload in the past.

[kadrim]

for me it was only a temporary fix.

After a few days the upload queue was not filled anymore. so i had to disable and renable the permission again to fill the upload queue.

has anyone else experienced this behaviour?

[mainframed]

I'm having the same issue. For a while the camera preview in 'Auto upload' it didn't show the new images i've taken for months, resetting the permissions fixed that but it still won't upload them. I know upload works cause I tested it on a different folder and it uploaded those images.

This is on Android 10.

[MatthiasJSchmidt]

Same issue here on Huawei.
New installation solved it only temporarily.
After some days it stopped again uploading new files.
Vary sad situation, as this is main the reason of using this app for me.

Btw. On Samung it still works.

[xaavro]

On my Poco F1 I have to force stop and renew permissions every few days or else it eventually stops auto-uploading files.

[kescherCode]

None of the proposed fixes in this issue work for me, sadly. Nevermind. One hour after trying all fixes, it randomly started working. Guess I will do this every evening.

Redmi Note 7 on Android 10, LineageOS 17.1.

[Karlish-git]

Fix mentioned here don't help. Can't open the "shared" tab

App information

• ID: com.nextcloud.client
• Version: 30200190
• Build flavor: gplay

Device information

• Brand: OnePlus
• Device: OnePlus6
• Model: ONEPLUS A6003

Firmware

• SDK: 30
• Release: 11
• Incremental: 2111252325

[thniels]

Client: Nextcloud v3.20.1 on Nokia XR20 w/ Android 12. Server: 23.0.5 with TLS1.2 and TLS1.3

My latest successful upload is from the 16th of May. However, what is curious is that only media files appear to be affected. Other automatically uploaded files come through okay, such as backups of misc. app settings. Also, files that are manually up- or downloaded work fine too (also files that are copied to the Photos folder in Nextcloud). I have tried the mentioned workarounds but neither of them works.

[InfamousUser]

The only problem that has always existed is the autoupload, the rest is relatively fine usually.

[thniels]

What kind of log information is required to follow this issue? Or, more precisely, what do I filter for?

FWIW, I get this error when attempting to requeue..

Upload of /storage/emulated/0/DCIM/Camera/IMG_20220528_122336_HDR.jpg to
/Photos/Thomas/2022/05/IMG_20220528_122336_HDR.jpg: Unexpected 
exceptionjava.lang.NullPointerException: Attempt to invoke virtual method 
'void org.apache.commons.httpclient.methods.PutMethod.addRequestHeader(java.lang.String, java.lang.String)' 
on a null object reference
at com.owncloud.android.lib.resources.files.ChunkedFileUploadRemoteOperation.run(ChunkedFileUploadRemoteOperation.java:212)
at com.owncloud.android.lib.common.operations.RemoteOperation.execute(RemoteOperation.java:187)
at com.owncloud.android.operations.UploadFileOperation.normalUpload(UploadFileOperation.java:857)
at com.owncloud.android.operations.UploadFileOperation.run(UploadFileOperation.java:453)
at com.owncloud.android.lib.common.operations.RemoteOperation.execute(RemoteOperation.java:187)
at com.owncloud.android.files.services.FileUploader.uploadFile(FileUploader.java:640)
at com.owncloud.android.files.services.FileUploader$ServiceHandler.handleMessage(FileUploader.java:1396)
at android.os.Handler.dispatchMessage(Handler.java:106)at android.os.Looper.loopOnce(Looper.java:201)
at android.os.Looper.loop(Looper.java:288)at android.os.HandlerThread.run(HandlerThread.java:67)

[kadrim]

for me it was only a temporary fix.

After a few days the upload queue was not filled anymore. so i had to disable and renable the permission again to fill the upload queue.

has anyone else experienced this behaviour?

i have two devices, my samsung note9 and the samsung s9 of my wife. both uploaded the last images on may, 31th. since then nothing. reapplying the "workaround" helped again, so the new pictures were almost instantly queued.

this is a quite odd problem here.

[mepreston]

is this going to drag out for a over a year like issue #7400 did? I'd have more confidence that it might get resolved if someone was assigned to this issue. You already have enough comments on this issue to know it is not just a few people having issues. people aren't going to want to use nextcloud server if they can't use the mobile client features.

[Zocker1999NET]

I can confirm this issue on a Gigaset GS5 / Android 11 / Stock ROM (with Google Play Services, …) / Nextcloud installed from Google Play. I cannot even configure auto upload because Nextcloud never stops to search for directories:

Screenshot from Gigaset GS5 Nextcloud never stops searching for media directories


Funny enough, on a OnePlus 3 / Android 11 / Lineage OS 18.1 (with microG) / Nextcloud installed from F-Droid, auto upload still seems to work, at least I can see which folders contain images and configure them.

[udvarit]

I have the same issue, but only with a single photo. Every photo before, and after that auto-uploaded successfully.

Android version: 10 Device model: Galaxy S9 Stock or customized system: /e/ 1.0 (e-1.0-q-20220527189323-dev-starlte) Nextcloud app version: 3.20.2 Nextcloud server version: 24.0.1 Reverse proxy: no

E UploadFileOperation: Upload of /storage/emulated/0/DCIM/OpenCamera/IMG_20220614_210912.jpg to /Photos/IMG_20220614_210912.jpg: Unexpected exception
E UploadFileOperation: java.lang.NullPointerException: Attempt to invoke virtual method 'void org.apache.commons.httpclient.methods.PutMethod.addRequestHeader(java.lang.String, java.lang.String)' on a null object reference

Also, disabling then enabling the Storage permission didn't work.

[DEvil0000]

Auto upload does not recognize new .jpg images in the camera directory as images to upload. HD-Kamera App Nokia 9 Android 10

[devdvd]

I have the same issue like mepreston Nextcloud server version: 24.0.1 I already remove the permission on the app. I removed and reinstalled it from f-droid but same error. I removed it and installed the dev Version from april, same error. Then i installed the latest version again and i have the same problem. If i copy the photos to my windows pc the sync process from the Windows Machine works fine, so i think it's not direct a server problem.

E UploadFileOperation: Upload of /storage/emulated/0/DCIM/Camera/PXL_20220619_100538962.jpg to /SofortUpload/DCIM/2022/06/Camera/PXL_20220619_100538962.jpg: Unexpected exception E UploadFileOperation: java.lang.NullPointerException: Attempt to invoke virtual method 'void org.apache.commons.httpclient.methods.PutMethod.addRequestHeader(java.lang.String, java.lang.String)' on a null object reference

[giovannifanzaga]

Almost same problem here: cannot upload/auto-upload files (in app error and continuos notification badges). Translated error: "Upload conflict file: choose version"

Device: Oppo Find X3 Lite 5G Android 12 Nextcloud 3.20.3

Server: Ubuntu 20.04 Nextcloud 24.0.1 (Archive version - no docker/snap) Almost plain configuration (only Sectigo SSL wildcarded cert and "data" folder simlinked)

Devices and server on same LAN/subnet

Client installed on Windows works perfectly Browsing Nexcloud with a WebDav client (like this one: https://play.google.com/store/apps/details?id=com.schimera.webdavnavlite) from the phone, I can create/delete/rename/upload/etc all files/folder on the server, I think is not a server related issue. The android app can browse, create and delete folder, but not rename them. It cannot upload any kind of file, but it can create/edit/delete text (.md) file, but not rename them ("toast" error translate: file already present).

I tried uninstall/install several times, change permissions, battery optimisation with no results.

Dive into log files, the only "weird" thing that I found are these Apache's log lines:

Android app related log [45/Jun/2022:00:00:00 +0200] "PROPFIND /remote.php/dav/files/removed// HTTP/1.1" 207 1944 "-" "Mozilla/5.0 (Android) Nextcloud-android/3.20.3"

WebDav Nav Lite related log [45/Jun/2022:00:00:00 +0200] "PROPFIND /remote.php/dav/files/removed/ HTTP/1.1" 207 1282 "-" "WebDAV Nav Android/CPH2145/2.2.4"

The android's URI seems "malformed" (I don't know if it makes difference): just after the username (removed) there is a double slash (//) instead the single present in the WebDav Nav app. The "double slash" is present in almost Nextcloud app calls to the server.

[FrenkyIO]

Same issue with my Huawei P30.

Is there any new information on this?

[strugee]

Hi all! Please don't add +1 comments, as they don't contribute anything to the discussion and just generate more email for the maintainers (and those who are subscribed to this issue) to go through. Instead, you can support issues by using GitHub's reactions feature (smiley icon at the top-right of each comment).

If there were any updates, you would see them in this GitHub issue.

@AlvaroBrey seems like it might be a good idea to backport nextcloud/android-library#912 to stable so at least people hitting that issue stop commenting here/in case that's what's breaking auto upload?

[mepreston]

i suspect you are getting all these +1 comments because git doesn't show this assigned to anyone. even if someone is working on it they are not providing any updates in this ticket so everyone is assuming this is just being ignore like the ipv6 issues was ealier this year.