You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There may be times when a user wishes to keep automatic backups turned off for various reasons, such as travel.
In my case, which is admittedly out of the norm, I am testing Seedvault with a USB flash drive, and I want to be able to unplug and plug in the drive and be sure that Seedvault is not going to perform a backup at any time. This is because I want to restore the data in secondary users and want to ensure no clobbering happens.
Right now, there's no way to turn off app backup without requiring a reinitialization of backup data after turning it on again.
Ideally for me, there would be a feature to pause automatic backups that also makes it obvious that they are paused and nudges the user to turn them back on, e.g. a banner in the Seedvault settings screen in addition to a notification in a channel that the user can turn off if they really don't want to be bothered about it.
The text was updated successfully, but these errors were encountered:
There may be times when a user wishes to keep automatic backups turned off for various reasons, such as travel.
In my case, which is admittedly out of the norm, I am testing Seedvault with a USB flash drive, and I want to be able to unplug and plug in the drive and be sure that Seedvault is not going to perform a backup at any time. This is because I want to restore the data in secondary users and want to ensure no clobbering happens.
Right now, there's no way to turn off app backup without requiring a reinitialization of backup data after turning it on again.
Ideally for me, there would be a feature to pause automatic backups that also makes it obvious that they are paused and nudges the user to turn them back on, e.g. a banner in the Seedvault settings screen in addition to a notification in a channel that the user can turn off if they really don't want to be bothered about it.
The text was updated successfully, but these errors were encountered: