App was working fine yesterday.

I am on ios 10.3.2. After the update day yesterday, I can not use the app and not use the authenticator for my various logins, need a fix ASAP!

I have an iPhone 5c on iOS 10.3.3 running version 2.1.1 of the authenticator app.

I have one entry which was added via the QR code which worked fine.

I am now trying to add a new entry manually. I click the + symbol in the bottom right which loads up the camera. I then click on the "new entry" button in the top right to manually add data. The screen goes black and the app quits.

I cannot update my iOS version as Apple do not support this device any more. I tried restarting my device and that did not fix the issue. I am not sure how to turn on crash reporting if I am honest.

Happy to provide any additional information needed 🥇

Hi Matt, I didn't save the token when I used the 6-digit code I was given. And, I didn't write down the code either. Is there a way to find it or a floating token (she says with wry smile) somewhere in the recesses of my phone? I can't access my account without a numeric code. Any guidance you can give this beginner (seriously, my first attempt at this crazy business of authenticating) would be most appreciated. Many thanks.

I just restored an encrypted backup from an iPhone XS Max to an older iPhone 8 Plus and none of the 2FA tokens were restored!! The backup was encrypted and stored locally on my Mac. I still have access to the encrypted backup. Please advise how I can get the codes back. Thank you.

Also, please advise on where/how the tokens are stored, in case I can restore them manually since I can always jailbreak the original iPhone to retrieve them from the filesystem if necessary.

As of today I am up to 31 codes in the app. This poses user experience challenges when looking for a specific code as I this is almost 5 pages of codes. I know I can manually rearrange the codes, but it'd be nice to have some other out of box or usability enhancements.

Some ideas:

• A search box/option - Allow a user to quickly locate a specific code by filtering them
• Sort options - Allow a user to sort the codes, without manually rearrange them.

I'm open to other ideas, such as #257 and #249 which would help in different ways.

Purely an opinion but I find it easier to read two groups of three digits vs three groups of two digits.

And for 8 digit length codes I would say two groups of four digits would be better than four groups of two digits.

This change groups any code divisible by three into groups of three, divisible by two in pairs, otherwise no groupings.

TL;DR: This PR adds a settings screen that allows the user to choose whether they prefer passwords rendered in groups of two digits or groups of three.

This PR is the result of two separate issues I've been thinking about for a long time:

1. Version 2.0 of the app changed how passwords are displayed: instead of showing the whole password as a single string of digits, the passwords are chunked into two-digit groups to make them easier to read and remember. Since then, several users of the app have reported that they have an easier time remembering six-digit passwords when they are chunked into groups of three digits. A pull request from @beaucollins proposed to change the chunk size dynamically based on the length of the password, but despite the cleverness of this approach, it never quite felt like the right solution to me. I avoided making any changes on this for almost a year, for a very simple reason – I personally find it much easier to read and remember passwords chunked into groups of two, and the handful of users I had originally asked for input felt the same way. (At least one user wrote in an App Store review that the two-digit grouping is the specific reason they use Authenticator over other two-factor apps.) I have been reluctant to make any changes when the current two-digit chunking strategy has been working for (anecdotally) most users.
2. As long as I have been developing Authenticator, I have tried to keep the app as simple as possible. I want the app to be clear and straightforward for users, and I didn't want to add a settings screen with a bunch of potentially-confusing options. In addition to complexity for users, adding user settings increases the number of different states in which the app operates, and can make testing and debugging significantly more complicated. For these reasons, I've avoided adding a settings screen to the app.

After thinking over the best way to present passwords that are readable and memorable for all users, I've concluded that the solution is to overcome my reluctance to add a settings screen to the app, and to add a toggle allowing the user to pick how they prefer for passwords to be grouped. Currently, the options are groups of two digits or groups of three digits. If I receive further user feedback on the issue, I will consider adding more options, but for now I want to keep things as simple as possible. While I think the approach of changing the chunk size based on password length is aesthetically pleasing, I have found in my conversations with users that preferred chunk size for ease of memorization seems constant for a given person, regardless of password length.

I would love to hear what people think of this approach, and in particular to know whether this is is a satisfactory solution for those who prefer passwords in groups of three digits.

Hello, I tried to get an authentication code today. I tapped on my app on my iPhone as usual and instead of a code appearing, the message "No Tokens" "Tap + to add a new token" appears. How do I fix this so that I can get to my email account? Kind regards, Jennifer

Based on the excellent work by @beaucollins in PR #224. My changes on top of that PR can be seen here.

Currently, the app animates the progress ring and keeps token passwords up-to-date by using CADisplayLink to regenerate the view model and update the view at 60 frames per second. This is needlessly inefficient, and causes excessive processor load. Instead of updating the view every frame, it is sufficient to generate a new view model only when a token password has updated, and to use Core Animation to drive the progress ring.

Animatable Progress Ring

The drawing code for OTPProgressRing has been moved to a custom CALayer with an animatable progress property. The TokenListViewModel's ringProgress property has been replaced with a ProgressRingViewModel which specifies the start and end times of the current cycle of the animation. These values are used to configure a CABasicAnimation which drives the ring animation, removing the need for constant updates from a CADisplayLink. The progress ring now only needs to be updated with a new view model when a new cycle of the animation should begin.

View Model Expiration Date

The method which generates a view model for the token list (and for the root component) now returns a tuple containing both the view model and a nextRefreshTime. The AppController's display link has been replaced with a refresh timer, which is configured to fire at the nextRefreshTime and trigger an update of the view with a new view model.

The app also now triggers a view update on applicationWillEnterForeground, to ensure the UI is up-to-date when the app returns from the background.

Future Performance Considerations

These changes reduce idle CPU usage from around 40% to less than 10%. The remaining CPU load is almost entirely caused by animating and redrawing the progress ring. Ideas for optimizing the drawing of the progress ring are discussed below.

The website I created a super safe password for ended up unable to read the app at first. So I tried again. It was able to read it the second time. So I figured I would delete the unreadable code to prevent future mishaps. Turns out, I somehow accidentally deleted the working code. Now, the website has me completely locked out due to being unable to authorize it with the app. How in the world can I reset it? Is there a way to reset it? Is there a way to remove this authentication from my account (even though I am locked out)? I spoke to the website support and they said I had to contact the app support directly. I am at a complete and utter loss here.

The app used to have two three-digit groups (123 456) and a recent(ish) change made it three two-digit groups (12 34 56). What was the motivation behind this?

I'd love the option to put it back to 123 456 as that is easier for me to remember.

Love the app! Super simple and nothing more than you need. (Plus the fact you can't export is perfect, the way it should be!)

Hi mate, hope you can help I have changed phones and has this app of yours as a 2 factor rolling code. I can fond my initial setup. Please help me to try get it fixed? Thanks Michail

Hello, I really appreciate your project, however it seems to have been abandoned since the last release was about 3 years ago. Is the project still alive? Do you have a roadmap? Thank you

In short: add the option to show a QR code (or copy/paste able secret key) to move a 2FA code to a new device and/or authentication app, with the caveat that Authenticator will delete it once moved.

This retains the feature/security opinion that having the same code in two places defeats the point of 2FA whilst making moving codes a lot easier.

Migrating to a new device can be a big pain, often because many apps and websites don't support renewing 2FA codes without also reissuing backup codes (which then take ages to write down if you prefer that to keeping a bunch of risky text files somewhere) or disabling and then re-enabling 2FA altogether which is (pedantically) a security issue itself. Not to mention the flurry of emails and notifications you have to clear up after renewing two dozen or so 2FAs.

Currently Authenticator only supports migrating to a new iPhone with encrypted backups, which is OK but has some limitations - not everyone uses that backup method as it requires a second trusted device to back up to, and you need to have a recent backup. Some users might prefer to not have their codes backed up at all, given paper recovery codes are intended to be used if a device is lost.

Secondly, this would allow for portability which IMO is a good thing, to allow moving to a different 2FA app if a user wishes to do so.

Note also that the current policy of including codes in encrypted backups does mean you kan skirt the rule of not having the same code on two devices, so forcing a code to be deleted once moved using this suggested feature may be unnecessary/not really more secure, and instead the app would just strongly suggest deleting it once moved.

I love your authenticator app. Fits the requirement of most companies (being offline, opensource etc.).

One thing that would make it even better would support for widgets, like for instance: https://apps.apple.com/dk/app/authenticator-app/id1538761576

Hello I used to have a token for Facebook 2FA. Now it is gone for some reason but my others are still there. Anyway I can recover it? Facebook says this is the only way to get in.