iOS 7 - Added accounts don't save, are wiped when app is removed from taskbar/device is rebooted

[ThomasHabets]

Original issue 278 created by stefanmodh on 2013-06-24T20:40:25.000Z:

What steps will reproduce the problem?

1. Run iOS 7 (Beta 2 as of writing)
2. Add an account in the app
3. Reboot device
4. The added account is no longer saved within the app and will need to be re-added.

What is the expected output? What do you see instead? Accounts should be saved for persistent granting of auth codes, they're not.

What version of the product are you using? On what operating system? iOS 7 Beta 2, iPhone 5 model A1429. Using v1.1.4.757 of the Google Authenticator app

Please provide any additional information below.

[ThomasHabets]

Comment #51 originally posted by r.ellis.michael on 2013-09-04T04:52:36.000Z:

Confirming that all of the accounts are wiped on update.

[ThomasHabets]

Comment #52 originally posted by simonk83 on 2013-09-04T05:01:50.000Z:

Mine too, pretty pissed. Is there a way to get them back?

[ThomasHabets]

Comment #53 originally posted by indermohan on 2013-09-04T05:03:18.000Z:

I should have checked it's all wiped what the hell???

[ThomasHabets]

Comment #54 originally posted by franck.arnulfo on 2013-09-04T05:14:41.000Z:

Le mercredi 4 septembre 2013, a �crit :

[ThomasHabets]

Comment #55 originally posted by simonk83 on 2013-09-04T05:24:53.000Z:

Will installing the old version (if I can find it) restore the auth's as well? Otherwise how on earth do you get back into sites that you've enabled 2FA on?

[ThomasHabets]

Comment #56 originally posted by mark@markgthomas.net on 2013-09-04T06:37:30.000Z:

I got an update todayand it seems to be saving the accounts properly now. Use your backup codes, log in, and then re-add the accounts. Annoying, but hardly severe.

I don't like the new grey and white icon.

[ThomasHabets]

Comment #57 originally posted by simonk83 on 2013-09-04T06:40:16.000Z:

Doesn't get much more severe. Sure it's fine if the site in question offers backup codes or some sort of recovery, but not all do.

Sure, that may be the sites fault, but how about we don't issue updates without testing them for huge bugs.

[ThomasHabets]

Comment #58 originally posted by mark@markgthomas.net on 2013-09-04T07:02:03.000Z:

A site that doesn't use backup codes? I'd like to see that site. That's the site that's never run into the use case of someone whose phone died.

In the meantime, this started out as a bug report and has turned into a chain of rants. Let's review, shall we? The 2FA app that Google makes available for free was ready only a week or so ahead of the predicted release of iOS 7. Those of us who installed the BETA version earlier than that on devices we depend on...well, it wasn't a question of IF an app would have trouble, but WHICH ONES and WHAT KIND. So while I can empathize with everyone who has had problems..."beta" is not a brand name.

[ThomasHabets]

Comment #59 originally posted by simonk83 on 2013-09-04T07:30:20.000Z:

Mm. That's lovely, aside from the fact that they've issued an update today for ALL iOS versions (I'm on 6) that wipes all codes unnecessarily and without warning.

However you look at it, that's unacceptable. Clearly none of the app developers thought to test upgrading from an older version, which is what the majority of people installing it will be doing. That's shoddy work for even the smallest developer, let alone google.

No acceptable excuses for this unfortunately.

[ThomasHabets]

Comment #60 originally posted by bpaluzzi on 2013-09-04T08:36:57.000Z:

@# 58 - Amazon AWS doesn't use backup codes.

This is a severe problem from Google. FYI - Authy is free.

[ThomasHabets]

Comment #61 originally posted by jhatrs on 2013-09-04T10:24:11.000Z:

Just received an email from Amazon Web Services warning me of the problem with the Google   Authenticator (as if I didn't already know). Apparently they've started receiving complaints from customers about it.

On Wed, Sep 4, 2013 at 1:14 AM, null google-authenticator@googlecode.com wrote:

[ThomasHabets]

Comment #62 originally posted by Jan.Willhaus on 2013-09-04T10:39:45.000Z:

@# 61 Indeed. Just had a support representative call me back, to regain access to my AWS account, since Amazon does not provide backup codes. He told me they get a lot of tickets over this issue today.

[ThomasHabets]

Comment #63 originally posted by mstanislav@duosecurity.com on 2013-09-04T14:17:26.000Z:

Just start using Duo Security's mobile app (http://guide.duosecurity.com/third-party-accounts) that's actually updated more than once every two years and isn't an after thought like Google's Authenticator app. Google's 2SV and any TOTP-based two-factor services are supported. iOS 7 works just fine, as well.

[ThomasHabets]

Comment #64 originally posted by mark@markgthomas.net on 2013-09-04T15:47:48.000Z:

Neither Duo nor Authy support counter-based key generation, so if you need one of those (which I do) you'll have to keep Google Authenticator.

[ThomasHabets]

Comment #65 originally posted by jhatrs on 2013-09-07T14:15:21.000Z:

Just downloaded version 2.0.1.2118 of the Google Authenticator for iOS, and it appears that the issue has been resolved in that version.

[ThomasHabets]

Comment #66 originally posted by jptsetme on 2013-12-12T14:28:29.000Z:

I'm late to the complaint party, as I delayed installing ios7 for various reasons.

I had the same issues described above (account names not listed in Google Authenticator, and then accounts started disappearing.) I went to the app store and installed the update, and both of these issues are fixed. (I now see account names, and the accounts that had disappeared have reappeared.) Still weoful that it took a long time to be addressed, but if you're just seeing this issue now, update and you'll be fixed.