"Auto Backup" doesn't work as expected

[dmnsea]

Describe the bug
Auto backup description says:

Backups are scheduled when changes are made.

But doesn't clarify which changes being tracked. And autobackups actually happens not when they expected to be.

To Reproduce
Steps to reproduce the behavior:

1. Go to 'Auto Backup' settings
2. Choose folder for backups
3. Set password for backups
4. Return to main screen
5. Add new authenticator by given key
6. No notification or toast about backup in 30 seconds
7. Backup folder still empty
8. Returned back to Stratum
9. Appeared notification about backup done
10. Backup file appeared
11. Any new authenticator added actually not being backuped until i switch to some other app and return to Stratum open Stratum next time
12. Same when editing (e.g. renaming provider, user) or deleting existing authenticator
13. Assign (or unassign) any amount of categories - no backup done even if switched to some other app and back to Stratum

Expected behavior

• Authenticator added => backup done
• Authenticator edited => backup done
• Authenticator deleted => backup done
• Categories changed => backup done

App Version
1.6.2 F-Droid

Additional context
I was going to switch from AndOTP, but behaviour of autobackup feels "weird" and due to that - unreliable. If i add authenticator, closed Stratum and don't open it before something happened with device - actually no backup done and I'm gonna be stuck with 2FA enabled and no existing backup to restore on any other device.

Also I want to ask exactly about description:

Backups are scheduled when changes are made.

Why scheduling? Why not write backup on change? It may be reasonable in the beginning, if user will transfer authenticator keys manually, but this most likely will hapen 1-2 times during all app usage. At all other times there won't be that much changes, to cause any issues.

I would understand scheduling in terms of automated cloud backups - to accumulate changes when user adds bunch of authenticators and send them once in ~1-2 mins, instead dozen of backups on each change. But Auto Backup description clearly states:

Cloud storage is not supported

Which means that all backups will be stored on device. There's no ratelimit, there's no huge delay for write, there's no single problem with writing backup right when change was made.