TouchID stopped working since iOS16 [Fixed. Please see the approved answer for details.]

LastPass does not have the same problems with FaceID and TOuchID that 1Password8 does. It may be time to make the switch. Exporting data is not terribly difficult.

The latest version was advertised with the great Touch ID feature. This will allow for longer and more secure passwords. Great! I can unlock my phone and every app I protected with Touch ID. The only app that is always asking me to first enter the password before I can use Touch ID is 1Password!
I don't think I keep this on my phone (SE 2020, latest IOS - 16.02) for long.

How long is this going to take to fix? Seems like it’s foot dragging with an elaborate “we’re working on it” excuse. Please identify when a fix is coming so I know whether to look at other options.

I am having a similar problem on my iPad (on iPadOS 15.7). I thought it was only with the Safari extension, but I tested the steps above, having set the security settings to Auto Lock on Exit to Immediately.

When I switch back to 1Password (step 4), it prompts me to use Touch ID, but then gives a little shake and says I need to enter my account password before I can use Touch ID.

This started because Touch ID does not come up as an option in my browser, even though the extension is installed and enabled. I have to enter my master password if it hasn't been used recently. I haven't timed the delay, but it's not long. It used to work, and works fine with FaceID on my iPhone.

Any help would be appreciated

GreyM1P Please let management know that there would’ve been FAR less frustration and agitation from your users over this issue if they had just come out with these detailed updates to begin with.

Thanks GreyM1P .. THIS is the information that was needed.. a while ago.. but.. a bit late than never I guess.

@xyzulu

Face ID and Touch ID in 1Password 8 on iOS are currently a very high priority for our development and customer support teams. The development team have found the cause of the problem and the relevant secure parts of iOS that 1Password communicates with. They are working on building a solution for the root cause of the problem and although it may not seem like it from the outside, there has been considerable discussion about this issue within the teams. I assure you, we do know about it, and the impact that it's having on customers. We're hoping to have something concrete to announce in that regard soon.

Up until now, there hasn't been anything suitably actionable we could suggest to help, so we have been gathering information about affected customers and letting them know that we're aware of the issue and are working on it. We do know that erasing the device, which also erases its Secure Enclave, then allows 1Password 8 to work with Face ID and Touch ID properly again, even if restored from backup, since the Secure Enclave isn't backed up. However, that's a very drastic step, and involves erasing the entire device – something we wouldn't actively recommend to customers. It is hardly a proportionate workaround, and has the potential for serious data loss, so we haven't offered it publicly to customers. However, it's helped the development team gain valuable insight into what's causing the problem.

When you asked for "an update on the original poster's issue", I was under the impression that you were asking about the issue experienced by the original poster specifically, rather than the issue more broadly. Apologies for the confusion there.

Any customers who have reported experiencing this issue to us will be updated directly when the fix is available. Those who haven't can check the 1Password Releases blog, and can look out for mention of the issue there.

We'd like to thank everyone for bearing with us while we get this fixed. Because the problem involves talking to the Secure Enclave – the security chip in iPhones and iPads – it's not a straightforward process to diagnose and troubleshoot, since we're not able to dig around in the same way that we can in our own code. Fortunately, we now have the answers we need, and are now past the investigation stage and are moving into the resolution stage. Please stay tuned for further updates when we have them. You'll either hear from us directly, or via the release notes in the App Store when 1Password updates, or you can check the 1Password Releases blog to see what's new.

Unfortunately, everyone is seeing what happens when a company gives up control of the company to the providers of venture capital. Quality takes a huge hit and is forced to take a back seat to quantity. Sadly, AgileBits is no longer the company that we knew, loved, and most of all trusted. I believe the co-founders have been relegated to a minority position, and no longer have any true saying in the development and operation related to 1Password.

GreyM1P 2 months after you knew about this issue.. that is all you share? And in a reply to a thread.
No announcement here in the community about this issue. No blog post. No support article. No message in the app store.
Many staff still clueless there there is even an issue. You can't see why we are feeling frustrated?

"we have made significant progress in solving the issue with Face ID and Touch ID in 1Password 8 for iOS and we hope to have good news about this soon."

You wrote:
"I can't comment on another customer's case for privacy reasons.."
Thanks for the patronising reply. I never asked for private information. I asked why you had not provided an update. Stop trying to divert attention.

Moving to LastPass will not be fun, but that is the direction that the 1Password folks are pushing me.