Jonas Mayer

Problem: With current implementation when periodic sync worker is started and immediate filesync is already running because of changed files it will skip periodic sync which is not intended... But...

So Ideas to fix these issues would be to: 1. Make sync worker only check things changed on file system, not whole folder each time. Make a whole rescan of...

> 1. Make sync worker only check things changed on file system, not whole folder each time. Make a whole rescan of the folder only once per day instead of...

@regs01 it goes through every autoupload folder recursively and checks if the last modified timestamp is larger than the last scan (at least that's the behavior with the next release....

Hmm I can't reproduce here, could one of you check if this issue still exists with the new 3.29 RC1 and if yes check if it already existed in 3.28.0....

@mintsoft yes on master a lot has changed there. That's why it would be interesting if this issue exists on 3.29 RC1 too.

Hi, possible duplicate of https://github.com/nextcloud/android/issues/12641? @ericzolf I think you are describing this https://github.com/nextcloud/android/issues/12358 issue, or do you experience a new issue?

Hi all, thanks for the report. ### Analysis Yes, this behavior of showing a notification when ever sync work is done (so also checking if files need to be uploaded)...

@larena1 thanks for mentioning me. I will have a look 👍

@larena1 you might be right that the launchMode is not needed, but this new behavior is introduced by the taskAffinity="". At least in my testing, reverting the general launchMode changed...