Cloud Backup and Sync

[debug-cli]

Just like Google authenticator, I think it is REALLY important to have those keys saved in the cloud. So if your device gets wiped and you cant have a code on Mauth and Google auth on the same time, the codes may be long gone.
At least add Log in with Google or just connect it to Google auth so the actual code for the mauth authenticator login which has more codes.

[Bytezz]

Doing a regular export of encrypted file(s) (like described inside ReadMe features todo list) inside a user configured folder would be enough, paired with something like syncthing.

[zpc0]

This app should be without NETWORK permission like Aegis, please.

[X1nto]

This app should be without NETWORK permission like Aegis, please.

The network permission doesn't necessarily mean that the app accesses the network all the time. It's just there to show that it can access when it needs to. You can just keep the app from accessing the internet, modern ROMs allow you to disable network access per-app basis.

[Bytezz]

I would feel more comfortable with such an app without network permission at all.

[debug-cli]

I would feel more comfortable with such an app without network permission at all.

Why? Dosen't it need network permission to get the codes and function in general?

[Bytezz]

Why? Dosen't it need network permission to get the codes and function in general?

Codes are generated offline using known algorithms plus a secret key. These infos can be entered into the app by hand or by scanning a qr code containing those info. Network is never involved in the process on the app side.

[X1nto]

Why? Dosen't it need network permission to get the codes and function in general?

2FA authenticators work offline.

[RGBCube]

Backing up to a Nextcloud instance would be a great feature. It supports WebDAV so it shouldn't be hard to do.

[debug-cli]

It's been a while so i am just going to close this issue since i don't think the repository owner will do anything about it soon.

[X1nto]

You know, just because an issue is open, it doesn't mean I have the opportunity to address it as early as possible. Similarly, just because I didn't implement the functionality now, it doesn't mean it won't come ever. The purpose of issues isn't just to add stuff to the app, issues exist to avoid requesting the same thing multiple times. That being said, you closing this as "not planned" came out weird, as I never said I wouldn't implement it. People might come to the repository, search for closed issues, and find that cloud sync is apparently "not planned", which is not the case. I'll reopen this because I need something to track the feature with. If you desperately need cloud backup and sync, either switch to another app (be it temporarily or permanently), or feel free to PR the functionality and I'll be glad to review the code.