We have intentionally opted out of this[1][2] for now, since we did not want to create a dependency on iCloud for backups.

So if you purchase a new device, you will either have to sign in to Ente Auth again (for E2EE sync), or export your codes from the older device, and import it to the newer device.

[1]: https://github.com/ente-io/ente/blob/8b696b1242bce2f166ddd6a...

[2]: https://github.com/mogol/flutter_secure_storage/blob/cb30953...

Thank you. FWIW, my need comes primarily from non-technical/inexperienced users. I can't tell my parents/many friends to remember to "sign into all these apps" as soon as they get a new phone, or they loose access to banks & co. Regardless I appreciate that at least you made a conscious decision.

I’ve seen this happen. A family member set up google auth. Then later got a new phone. I know I’ve transferred google auth across phones in the past - although possibly over iTunes? The new iPhone setup process works differently I guess. My family member did the new transfer feature, then wiped the old phone. Then later discovered that they don’t have access to some important accounts, because google Authenticator was completely empty. Luckily they did actually have a physically printed backup copy.

> I know I’ve transferred google auth across phones in the past - although possibly over iTunes? The new iPhone setup process works differently I guess.

There were a few brief years where an encrypted iTunes backup was a perfect, universally-restorable image of an iOS device. You could back up an iPhone, pop out the SIM card, destroy the original phone, then pop the SIM into a new one, restore the backup, and it would be nearly-impossible to determine that the device was different from a daily UX standpoint. Even MS Exchange email sync would still work.

Then around the time that iCloud K/V store showed up (which may be coincidental), this stopped working. Every app would start up and ask you to log in. Email needs reauthentication. Encrypted iTunes backups aren't terribly useful anymore.

OTP Auth supports iCloud sync in the paid version.

The free version does too. The paid version only adds cosmetics, last time I checked.

I might be mixing that up with Strongbox. Either way, solid app and worth paying for.

> FWIW, my need comes primarily from non-technical/inexperienced users. I

Number one reason why most of my friends and family dont want to buy a new iPhone. They hate the pain and the anxiety of upgrading. And Apple hasn't done anything to make it easier.

It’s extremely easy these days.. you just put the phones near each other when prompted and follow the instructions.

Agreed with others here. It’s good that this was an intentional decision but I implore you to reconsider.

Thanks for the feedback, will reconsider.

From the documentation I found for kSecAttrAccessibleAfterFirstUnlockThisDeviceOnly, it sounds like what you are doing here is explicitly opting out of support for the usual secure mechanisms Apple users have to back up their device--such as an encrypted iTunes backup--which, to me, seems pretty egregiously wrong.

If you’re in the Apple/iOS ecosystem and want the syncing to happen via iCloud, you might as well use Apple’s built-in password manager which has support for 2FA codes.

Just because your in the Apple ecosystem does not mean your not outside it as well and want the crossplatform side.

Exactly. I use BitWarden for this reason.

Oh wow, I missed the release. Will def test it. I've been using authy since 2017, anything I said above might need a refresh :)

I use Tofu on iOS and it nicely migrated my tokens from a iPhone SE to a 13 Mini. It does not do iCloud backups, so it was a straight device to device transfer.