Cannot enable Touch ID on Mac Mini with Magic Keyboard

@Va1ha11a

It's the common folder name for 1Password 8's data files on all Mac devices. 🙂

-Dave

Yep, that was the string above. Just wasn't sure if the installation folder was user-specific for whatever reason.

@Va1ha11a

I'm happy that the team was able to resolve the issue for you. If the string in step 5 was "2BUA8C4S2C.com.1password" then this will be common to all Macs and isn't related to you, your account, or your Mac.

That being said, I recommend that anyone else running into this issue in the future please send in a diagnostics report to support@1Password.com before implementing those steps.

-Dave

Thank you! Support was able to resolve my issue. For anyone experiencing the issue, here's the steps I took to resolve the issue:

1. Please ensure that your data at my.1Password.com (in a web browser) is correct and complete. If it's not please do not proceed and let me know.
2. Fully quit any browsers that you have open. Right-click the 1Password icon in the menu bar (if it's there) and click Quit.
3. Open the Finder app
4. In menu bar, select Go menu > Go to Folder...
5. In the box that appears, copy and paste the following exactly and press Return: ~/Library/Group Containers/[RANDOM_STRING_THAT_MIGHT_BE_A_UNIQUE_ID_HERE].com.1password/Library/Application Support/1Password/Data/1password.sqlite
6. Right-click on the 1password.sqlite file appears, and select Compress "1password.sqlite".
7. Drag the original, uncompressed sqlite file to the Trash.
8. Open the 1Password app.
9. Check if you are able to turn on Touch ID under Settings > Security afterwards?

The part in brackets in step 5 was a random-looking string of letters and numbers that could be a unique ID, so I've removed it from my post. If you're not sure what to put, navigate to ~/Library/Group Containers/ and find the folder whose name ends with ".com.1password".

Thanks so much @Va1ha11a and @fransbuiijsen !

Someone from our team will be in contact with you as soon as possible.

• Alvin

ref: RNQ-37786-614
ref: TFC-31384-447

Hello ag_tommy, I have received support ID number [#TFC-31384-447]

Hi ag_tommy, my support ID number is [#RNQ-37786-614]

Thank you!

@Va1ha11a

I'd like to ask you to create a diagnostics report from your device:

1. Open 1Password.
2. Press command and comma. The 1Password preferences will open.
3. Tap Advanced.
4. Click Send Diagnostics.
5. Click Reveal to locate the report in your downloads folder.

Attach the diagnostics to an email message addressed to support+forum@1password.com.

• Your forum username: Va1ha11a

• A link to this thread: https://1password.community/discussion/139876/cannot-enable-touch-id-on-mac-mini-with-magic-keyboard#latest

• Please do not post your diagnostic report to the forum. This is for your privacy and security.

You should receive an automated reply from our BitBot assistant with a Support ID number. Please post that number here. Thanks very much!

@fransbuiijsen

I'd like to ask you to create a diagnostics report from your device:

1. Open 1Password.
2. Press command and comma. The 1Password preferences will open.
3. Tap Advanced.
4. Click Send Diagnostics.
5. Click Reveal to locate the report in your downloads folder.

Attach the diagnostics to an email message addressed to support+forum@1password.com.

• Your forum username: fransbuiijsen

• A link to this thread: https://1password.community/profile/fransbuiijsen

• Please do not post your diagnostic report to the forum. This is for your privacy and security.

You should receive an automated reply from our BitBot assistant with a Support ID number. Please post that number here. Thanks very much!

I'm having the same problem of the greyed out TouchID box. I've followed the steps give by Dave_1P listed here: https://1password.community/discussion/135021/touch-id-on-macbook-pro-not-working-after-upgrade-for-1p7-to-1p8. Unfortunately, that didn't fix my issue. I can go ahead and submit send a diagnostic report via Dave_1P's second message in that thread if that will help debug. Thanks!

Looking through the logs generated (I know not to post the full logs, I'm just posting a single line without PII), it looks like the issue may have something to do with the following:

System biometry info: BiometricStatus { current_policy: BiometricsOnly, current_method: TouchId, current_availability: EnrollmentChanged }

Earlier log entries (from 4/20 and earlier) note:

System biometry info: BiometricStatus { current_policy: BiometricsOnly, current_method: TouchId, current_availability: SensorUnavailable }

Going back all the way to 4/6, I can find entries that say

System biometry info: BiometricStatus { current_policy: BiometricsOnly, current_method: TouchId, current_availability: Available }

Does this mean something has been hogging the sensor since 4/6? Given it's also throwing enrollmentChanged, that could be the enrollment service within MacOS?