# TouchID Error on new Macbook Pro **URL:** \ **Category:** Issues\ **Created:** [January 23, 2022, 4:39am UTC](https://discuss.zetetic.net/t/touchid-error-on-new-macbook-pro/5270 "2022-01-23T04:39:00Z")\ **Posts on this page:** 8\ **Page:** 1
**Author:** ![sarahmcvean](https://sea2.discourse-cdn.com/flex016/user_avatar/discuss.zetetic.net/sarahmcvean/32/149_2.png) [@sarahmcvean](https://discuss.zetetic.net/u/sarahmcvean)\ **Post date:** [January 23, 2022, 4:39am UTC](https://discuss.zetetic.net/t/touchid-error-on-new-macbook-pro/5270/1 "2022-01-23T04:39:00Z")
I had to go from TouchID Macbook back to pre-touch ID Macbook and now I am on a new Macbook with TouchID. When I moved back to my 2015 MBP I was getting a touched error on startup. I still get this error message when I log in with my new MBP with touch ID enabled. How can I fix? ![Screen Shot 2022-01-22 at 8.38.24 PM](https://us1.discourse-cdn.com/flex016/uploads/zetetic/original/2X/1/1201dddae1773ca088eea87c3435102610386b30.jpeg) ---
**Author:** ![mmoore](https://sea2.discourse-cdn.com/flex016/user_avatar/discuss.zetetic.net/mmoore/32/858_2.png) [@mmoore](https://discuss.zetetic.net/u/mmoore)\ **Post date:** [January 24, 2022, 3:18pm UTC](https://discuss.zetetic.net/t/touchid-error-on-new-macbook-pro/5270/2 "2022-01-24T15:18:06Z")
Hi @sarahmcvean Thank you for using Codebook and posting to the discussion forum, although I’m sorry to hear about the trouble. When you enable Touch ID within Codebook for macOS, Codebook stores your Codebook Master Password in the secure enclave to be retrieved using your fingerprint to login to Codebook. When transferring to a new device, this secure enclave doesn’t transfer. So from your description, I think this is an expected error: Codebook still has the Touch ID setting enabled, but there is no record in the secure enclave to retrieve. Not to worry though, you can use these instructions to re-enable it: 1. Login to Codebook using your Codebook Master Password. 2. Go to Codebook menu \> Preferences \> Locking Tab 3. Uncheck the “Enable Touch ID Login” checkbox, then re-check it. 4. Quit and re-launch Codebook and it should properly prompt you for Touch ID Login Let me know if that does the trick. Thanks! ---
**Author:** ![sarahmcvean](https://sea2.discourse-cdn.com/flex016/user_avatar/discuss.zetetic.net/sarahmcvean/32/149_2.png) [@sarahmcvean](https://discuss.zetetic.net/u/sarahmcvean)\ **Post date:** [January 24, 2022, 5:02pm UTC](https://discuss.zetetic.net/t/touchid-error-on-new-macbook-pro/5270/3 "2022-01-24T17:02:55Z")
That fixed it, thank you! ---
**Author:** ![mmoore](https://sea2.discourse-cdn.com/flex016/user_avatar/discuss.zetetic.net/mmoore/32/858_2.png) [@mmoore](https://discuss.zetetic.net/u/mmoore)\ **Post date:** [January 24, 2022, 5:05pm UTC](https://discuss.zetetic.net/t/touchid-error-on-new-macbook-pro/5270/4 "2022-01-24T17:05:45Z")
@sarahmcvean Glad I could help! Please feel free to reach out again if you have any further questions. Have a nice day! ---
**Author:** ![ZipFoxtaur](https://sea2.discourse-cdn.com/flex016/user_avatar/discuss.zetetic.net/zipfoxtaur/32/1228_2.png) [@ZipFoxtaur](https://discuss.zetetic.net/u/ZipFoxtaur)\ **Post date:** [February 16, 2022, 3:09pm UTC](https://discuss.zetetic.net/t/touchid-error-on-new-macbook-pro/5270/5 "2022-02-16T15:09:05Z")
FYI, this issue happened to me, but for a different reason. I injured the finger I normally use for TouchID, so I added a new fingerprint in my Mac’s Security settings. This seems to have invalidated TouchID entries for various software, including Codebook, leading to the above error. I am glad this thread was here, because I couldn’t figure out how to re-enable TouchID within Codebook. So you fixed my problem, too. Thanks! ---
**Author:** ![mmoore](https://sea2.discourse-cdn.com/flex016/user_avatar/discuss.zetetic.net/mmoore/32/858_2.png) [@mmoore](https://discuss.zetetic.net/u/mmoore)\ **Post date:** [February 16, 2022, 3:29pm UTC](https://discuss.zetetic.net/t/touchid-error-on-new-macbook-pro/5270/6 "2022-02-16T15:29:34Z")
@ZipFoxtaur Thanks for posting with your experience, and glad this post helped you to re-enable Touch ID within Codebook. Codebook does intentionally invalidate your keychain item for Touch ID Login when adding or removing a finger as a security measure. It may be helpful to add instructions to the error message for how to re-enable Touch ID when this occurs (i.e. Codebook menu \> Preferences \> Locking Tab \> Uncheck/Recheck enable Touch ID Login). I’ll bring this up with the rest of the team and we’ll add it in a future update if everyone agrees it’s appropriate. Thanks! ---
**Author:** ![Dan\_Danz](https://sea2.discourse-cdn.com/flex016/user_avatar/discuss.zetetic.net/dan_danz/32/278_2.png) [@Dan\_Danz](https://discuss.zetetic.net/u/Dan_Danz)\ **Post date:** [February 16, 2022, 4:05pm UTC](https://discuss.zetetic.net/t/touchid-error-on-new-macbook-pro/5270/7 "2022-02-16T16:05:25Z")
I, for one, think that **your original reasoning for invalidating is sound thinking**. Without it, a bad actor could merely register his own finger after the owner’s fingerprint and **break codebook security**. Perhaps an admonition to users to always register two or more fingers when creating a biometric login might be appropriate ---
**Author:** ![mmoore](https://sea2.discourse-cdn.com/flex016/user_avatar/discuss.zetetic.net/mmoore/32/858_2.png) [@mmoore](https://discuss.zetetic.net/u/mmoore)\ **Post date:** [February 16, 2022, 4:26pm UTC](https://discuss.zetetic.net/t/touchid-error-on-new-macbook-pro/5270/8 "2022-02-16T16:26:17Z")
@Dan_Danz > [@Dan\_Danz](#): > > I, for one, think that **your original reasoning for invalidating is sound thinking**. Without it, a bad actor could merely register his own finger after the owner’s fingerprint and **break codebook security**. Absolutely. I wasn’t suggestion on adjusting that behavior, apologies if my previous post was unclear about that. What I was suggesting was potentially including additional details for the error message when the keychain item doesn’t exist (after adding or removing a fingerprint for example) to direct the user on how to re-enable it within Codebook.