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

@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.