If OP updates he should also point out that they've fixed the issue now.
Done.
Topic: [SOLVED] Do not upgrade Google Authenticator (iPhone), you will lose keys! - page 2. (Read 18559 times)
September 08, 2013, 03:31:01 AM
Done.
September 07, 2013, 11:41:39 PM
LOSE
Please edit title OP!
Please edit title OP!
If OP updates he should also point out that they've fixed the issue now.
September 07, 2013, 07:33:14 PM
LOSE
Please edit title OP!
Please edit title OP!
September 07, 2013, 07:20:08 PM
+1
Update 2.01 restored keys.
Update 2.01 restored keys.
September 07, 2013, 10:39:00 AM
I can confirm that the recent update (2.01) works fine and the keys are safe... 
I will try again... but I'm a little scary
Edit: I confirm now it is working
September 07, 2013, 06:55:20 AM
I can confirm that the recent update (2.01) works fine and the keys are safe...
September 07, 2013, 06:45:52 AM
They've released a new update. Its restore all my missing keys
September 06, 2013, 11:47:09 PM
I can't believe they wouldn't have better tested this before releasing it. It's google we are talking about here FFS!
September 06, 2013, 11:27:35 PM
Sorry to insist, but those who use Google Auth without a backup (paper or otherwise) shouldn't be allowed to use anything regarding digital finance.
WTF does digital finance have to do with something I only use for a single poker account, where the removal of Authenticator basically takes a week? I only use it with Seals With Clubs because I never terribly trusted it, because I don't keep substantial amounts of money there, and because it is easy enough to remove.
Anything substantial stays in an offline wallet with both an electronic and paper backup in a secure location.
Anyone at Google who released an "upgraded" that universally trashes all keys is the one who should be barred from ever rolling out another product again. Even a single test of this "upgrade" done before releasing it on a single device that previously had it would have made it blindingly obvious that it should not be released in its current form.
There are far better alternatives in any event, like Authy.
In my only previous experience with multi-factor stuff like this, it was to enter a workplace, where it was a physical dongle combined with a keypad entry. And any other place I have had to use shit like this in the workplace (briefly), it was a firing offense to back it up in any way, on paper or in any other form.
September 06, 2013, 10:20:55 AM
Blegh, I upgraded before I saw this thread. Everything is gone. I had a lot of codes in there. What a jerkoff from google, someone ought to be fired for this.
Sorry to insist, but those who use Google Auth without a backup (paper or otherwise) shouldn't be allowed to use anything regarding digital finance. Did you know that phones get lost, stolen, become bricks, fall and break, their memory can fail... Or maybe there's a buggy update that screws them over... Really, didn't you know that?
Seriously guys, I use google auth too, and first thing I do from the very first day I use it is to make backups of EVERY key, and BTW I scan the QR from the backup to be sure everything is OK. Do you even think and understand what you are doing before using something like that?
September 06, 2013, 10:04:36 AM
I don't update authenticator anymore.
September 06, 2013, 12:25:49 AM
Blegh, I upgraded before I saw this thread. Everything is gone. I had a lot of codes in there. What a jerkoff from google, someone ought to be fired for this.
September 05, 2013, 03:51:29 PM
Well it doesn't show up for me in the App Store as an available update, so that's good. Still using the old version.
September 05, 2013, 10:02:21 AM
This happened to me also. I was using Google Authenticator with an exchange. I upgraded to a new phone knowing that it would reinstall and import the setup for the keygen for the exchange. I wiped my old phone and sent it off for recycling. New phone came, set it up, and Google Authenticator did not reinstall. When I reinstalled it, it did not transfer the config for the exchange. So I tried a manual sync with my Google account. No luck, gone forever. Took me 2 weeks to get back into that exchange. Fuck you Google Authenticator.
September 05, 2013, 06:50:36 AM
I thought the secret code/QR code would recover any "lost" google auth issues.
So as long as I have a backup of the QR code used to generate a working Google Authenticator token... it really doesn't matter what Google does, I can always get some copy of Authenticator from somewhere at some time and I can simply rescan and log in to Bitstamp or Mt. Gox, or whatever...
Is this a correct assessment?
Yes it is. In fact you should have a paper backup (just print the QR code) of ALL your Google Auth tokens.
I guess I should have a Post-It note with all my passwords pasted to my monitor too.
What will you do in case you lose your phone? A paper backup for the Google Auth tokens is mandatory - you obviously do not stick it to your monitor, you store it in a secure place. If you are extra paranoid, you store it GPG-encrypted.
our phone can get lost, it can brick because of a failed update, etc. - Using Google Auth without a backup of the security token is plain and simply retarded. Your phone can get lost, it can brick because of a failed update, etc.
September 05, 2013, 02:55:39 AM
Titanium Backup. Android not affected.
September 04, 2013, 09:47:20 PM
Nope. None of it worked. Even after deleting and doing an app-specific restore, installing the old version of GA, the keys are still gone, apparently irretrievably. The whole fucking point of 2-factor is to keep the other factor solely on one physical object. I'd be a lot more pissed if I had real money involved. Google shouldn't just do shit they apparently have no fucking clue how to do correctly.
September 04, 2013, 07:16:39 PM
I have no clue about pretty much anything this thread is about, but I do have one crucial piece of advice that may help out:
If you've accidentally already synced your phone after updating, check your Recycle Bin (if on Windows). My experience with iTunes is that if it was syncing a newer version from the phone to the PC, the older version was merely recycled rather than deleted entirely. Delete the "new" version's *.ipa file from "My Music \ iTunes \ Mobile Applications", restore the old version from the Recycle Bin, and send that version back to the phone.
If you've accidentally already synced your phone after updating, check your Recycle Bin (if on Windows). My experience with iTunes is that if it was syncing a newer version from the phone to the PC, the older version was merely recycled rather than deleted entirely. Delete the "new" version's *.ipa file from "My Music \ iTunes \ Mobile Applications", restore the old version from the Recycle Bin, and send that version back to the phone.
September 04, 2013, 07:12:03 PM
I thought the secret code/QR code would recover any "lost" google auth issues.
So as long as I have a backup of the QR code used to generate a working Google Authenticator token... it really doesn't matter what Google does, I can always get some copy of Authenticator from somewhere at some time and I can simply rescan and log in to Bitstamp or Mt. Gox, or whatever...
Is this a correct assessment?
Yes it is. In fact you should have a paper backup (just print the QR code) of ALL your Google Auth tokens.
I guess I should have a Post-It note with all my passwords pasted to my monitor too.
September 04, 2013, 04:30:47 PM
I thought the secret code/QR code would recover any "lost" google auth issues.
So as long as I have a backup of the QR code used to generate a working Google Authenticator token... it really doesn't matter what Google does, I can always get some copy of Authenticator from somewhere at some time and I can simply rescan and log in to Bitstamp or Mt. Gox, or whatever...
Is this a correct assessment?
Yes it is. In fact you should have a paper backup (just print the QR code) of ALL your Google Auth tokens.
Jump to: