-
-
Notifications
You must be signed in to change notification settings - Fork 1.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Daily backup of contacts and calendar not working #9632
Comments
Today it worked. I think this is the problem: The app tries to always backup at the same time of the day. If the phone is offline at that moment, the backup doesn't work. But the app doesn't seem to care if it worked or not. It says that has done its backup in the settings and is finished for the day. What it should do is to either give an error message to the user or wait for connectivity and then retry. |
Sorry for my ignorance in responding, but I was skimming through this project and noticed some useful things that are related. Note I haven't looked at the code, and just the big overview issues, so this is sort of a guesstimate of a road map. I'd say first thing to look at is to actually check the backup status instead of the job start, or completion. If it's based on completion, that It might be as easy as not catching or re-throwing an error so the job fails instead of completes. This is important not just for no internet, but if there were any other sort of issue, even temporarily, during the operation. Long term, Backups should be done using WorkManager. If not it's issue #3147. Then, a WorkManager Constraint requiring network access should be added to the backup task. That will mean the backups won't even try to run when there is no network, and should automatically start when the network becomes available. The code willing still need to check for success, but that should at least mean that loosing service during backup hours won't mean the phone is never backed up. |
Apply network constrains to prevent daily backup job being started without network. Backup job restart is required to apply new constraints. Similar migration has been applied in the past, but migration manager does not support re-applying steps again. Migrations manager has been refactored to make migration step re-applying easier, as more job restarts can be required in the future. Fixes #9632 Signed-off-by: Chris Narkiewicz <hello@ezaquarii.com>
Apply network constrains to prevent daily backup job being started without network. Backup job restart is required to apply new constraints. Similar migration has been applied in the past, but migration manager does not support re-applying steps again. Migrations manager has been refactored to make migration step re-applying easier, as more job restarts can be required in the future. Fixes #9632 Signed-off-by: Chris Narkiewicz <hello@ezaquarii.com>
Apply network constrains to prevent daily backup job being started without network. Backup job restart is required to apply new constraints. Similar migration has been applied in the past, but migration manager does not support re-applying steps again. Migrations manager has been refactored to make migration step re-applying easier, as more job restarts can be required in the future. Fixes #9632 Signed-off-by: Chris Narkiewicz <hello@ezaquarii.com>
Apply network constrains to prevent daily backup job being started without network. Backup job restart is required to apply new constraints. Similar migration has been applied in the past, but migration manager does not support re-applying steps again. Migrations manager has been refactored to make migration step re-applying easier, as more job restarts can be required in the future. Fixes #9632 Signed-off-by: Chris Narkiewicz <hello@ezaquarii.com>
Apply network constrains to prevent daily backup job being started without network. Backup job restart is required to apply new constraints. Similar migration has been applied in the past, but migration manager does not support re-applying steps again. Migrations manager has been refactored to make migration step re-applying easier, as more job restarts can be required in the future. Fixes #9632 Signed-off-by: Chris Narkiewicz <hello@ezaquarii.com>
Apply network constrains to prevent daily backup job being started without network. Backup job restart is required to apply new constraints. Similar migration has been applied in the past, but migration manager does not support re-applying steps again. Migrations manager has been refactored to make migration step re-applying easier, as more job restarts can be required in the future. Fixes #9632 Signed-off-by: Chris Narkiewicz <hello@ezaquarii.com>
Steps to reproduce
Expected behaviour
Actual behaviour
Can you reproduce this problem on https://try.nextcloud.com?
I didn't try, but I guess this is a client problem, not a server problem
Environment data
Android version: 11
Device model: Fairphone 4 5G
Stock or customized system: Fairphone OS
Nextcloud app version: 3.18.1
Nextcloud server version: 20.0.11.1
The text was updated successfully, but these errors were encountered: