FYI: I updated google authenticator a while ago -- big mistake :/

General
1

I while ago I needed to run aurora store to update some android applications.

while doing that I also updated google authenticator…

… and today I would have needed that – but now it expects login to google,
– which does not work (and I think that as a feature, it wanted to store my keys to google).

previously it worked wonderfully, was fast and just served me keys to like 4 services
(or 3, as microsoft wants to do it differently these days).

anyway, if you have working google authenticator application don’t update.

and a question: if I remove the app and try installing older version, will I loose all keys…?

Should always remember: If it ain’t broken, don’t break it!

[EDIT] I’ll ditch google authenticator for SFOS native (that was just so easy at the time…)

2

While your message is good at making people think before doing an update, the actual message should be: use one of the excellent native SFOS apps to generate TOTP (Foil Auth, SailOTP).
Both apps allow to view/export stored secrets, so migrating them to any other service/app is always possible. No need for Google authenticator at all.

8 Likes
3

you’re right. I came to that conclusion.

2 Likes
4

If you still need Google authenticator to switch to something else, it may be possible to downgrade the app. Download an older version with Aurora store and then
appsupport-attach
pm install -r -d /path/to/apk.apk

2 Likes