In this guide, we will show you a workaround to fix the issue of being unable to add Security Keys on iOS 16.3. The Cupertino giant has recently rolled out the latest iOS update and its security enhancement feature has managed to grab the attention of the masses. Dubbed Security keys, it replaces the traditional six-digit verification code that you enter from an Apple device.
So if you have a two-step verification enabled on your Apple account [which you definitely should], then after entering the password, you will have to use a FIDO Certified security key to complete the authorization. Only after that, will you be able to log in to your account. And as you might have guessed, losing this key means you will no longer be able to access your account.
To overcome this, it is always recommended to have at least an additional security key in hand [you could have a maximum of six]. Weighing in the risks and benefits involved, many users did infact opt for this method but have reported that they are unable to add Security Keys on their iPhones running iOS 16.3. Whenever they are trying to do so, they are greeted with the “Unexpected error occurred” message. If you are also in the same boat, then this guide will help you out. Follow along for the fix.
Fix Cannot Add Security Keys On iOS 16.3
As of now, the only workaround that is spelling out access for some users involves trying to add the secure keys around 3-4 times and ultimately they will be added to your iPhone. So refer to the below steps to give it a try and then check out the results:
- Head over to Settings > “Password & Security” > “Add Security Keys”.
- Now follow the on-screen instructions to complete the setup process.
- You might have to try this around 3-4 times before it ultimately works out.
As of now, this is the only workaround that is helping users to fix the issue of being unable to add Security Keys on iOS 16.3. As and when we get hold of more tweaks, we will update this guide accordingly. Moroever, as far as the official stance on this matter is concerned, the developers are yet to acknowledge this issue, let alone give out any ETA for the rollout of a fix.
Jan
Tried it few times and still unknown error. I contacted Apple support, will see if there is any solution