Unlock with watch keeps asking for password

Thank you for posting the Support IDs! I see that the team has already replied to you hexatriene and one of my colleagues will reach out to you soon as well babaev. 🙂

-Dave

ref: ETU-96194-685
ref: GFQ-42539-534

Hi, I have the same thing happening :–( Emailed the diagnostics, support ticket id is GFQ-42539-534. Thanks!

Hi - I am having the exact same issue described above with the exact same versions of HW and software involved. I've emailed the diagnostics file as instructed above.

Your support ticket ID is ETU-96194-685.

Thanks!

Thanks froghammer.

We're glad to have you with us. It looks like my colleague Grey replied to you a bit earlier. Please continue the conversation with them.

ref: XSB-16214-156

1P_Tommy:
Your support ticket ID is XSB-16214-156.

Happy to help! Let me know if you need anything else (former software Product Manager)

froghammer

Thank you for the offer. It might not hurt to ask you to send a report. The team can verify you are experiencing the same issue and ensure you're not experiencing something new, which might delay a resolution for you further.

1. Open 1Password.
2. Press Command and comma (Control and comma on Windows). The 1Password Preferences/Settings will open.
3. Select Advanced.
4. Select Send Diagnostics.
5. Select 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: froghammer

• A link to this thread: https://1password.community/discussion/comment/714584/#Comment_714584

• 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 experiencing the same issue. Please let me know if I can provide additional information

Hello @jrschenck! 👋

I'm sorry that unlocking 1Password using your Apple Watch isn't working. This is indeed an issue that our development team is actively investigating. I've added your report to the internal work item open for the issue.

Hopefully the issue can be resolved in a future update soon. I'm happy that you found a workaround for now.

-Dave

ref: dev/core/core#30517

Apparently it is a problem with version 8.10.36. Rolling back to a previous version solves the issue.