You could after restore from backup.2fa but changes wouldn't be saved as handling for the invalidated secret key wasn't implemented (it is now).

Best course of action for users is to:
1 - Create a new backup
2 - Reinstall the app
3 - Restore from backup

This version includes a fix for KeyStore invalidation due to an oversight on our part. After a sufficient amount of time using the app the KeyStore encrypted vault.json file that stores all your 2fa codes would become unreadable due to SecretKey becoming invalidated, losing all your 2fa codes.

The goal of 2fa is to use the latest security practices while staying easy to use. Although we’re still far from the final release, the app will also be available on iOS. 2fa will eventually match Aegis in features. For now, choosing it lets you ask for what you want and how you want it.

The update also adds a Screen security toggle to block screenshots, app recording, and overlays, and changes the app launchMode to singleInstance.

Beta 3 includes a security countermeasure for Pixnapping (CVE-2025-48561). It overlays random noise on the one‑time password (OTP) to make extracting the code significantly more difficult. Google will release a permanent fix in the December Android security bulletin.