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
I have syncing enabled with Syncyomi, syncing automatically every time the app is opened, a chapter is opened or read, and every thirty minutes. Each time one of these occurs, a notification is shown.
Since a sync has never failed, I don't know if it would appear in a separate notification channel, but I assume it doesn't, given the name of the channel (simply, "Progress"). This means I cannot disable notifications for sync successes, without also being unaware of when a sync fails.
Presumably, this also applies to backups and restores, given that syncs are in the same notification category; I don't want to give up the ability to know when a backup fails in order to disable the constant "Syncing library complete" notification.
To go further, this should then also apply to backup and restores, having backup successes and failures be separate notification channels.
Describe your suggested feature
I have syncing enabled with Syncyomi, syncing automatically every time the app is opened, a chapter is opened or read, and every thirty minutes. Each time one of these occurs, a notification is shown.
Since a sync has never failed, I don't know if it would appear in a separate notification channel, but I assume it doesn't, given the name of the channel (simply, "Progress"). This means I cannot disable notifications for sync successes, without also being unaware of when a sync fails.
Presumably, this also applies to backups and restores, given that syncs are in the same notification category; I don't want to give up the ability to know when a backup fails in order to disable the constant "Syncing library complete" notification.
To go further, this should then also apply to backup and restores, having backup successes and failures be separate notification channels.
Other details
Related: #1152
Maybe related: #1280
Acknowledgements
The text was updated successfully, but these errors were encountered: