1Password give weird haptic feedbacks

Hello @BKrnk! 👋

Thanks for reporting the issue, it sounds like you're referring to iOS AutoFill (the "Passwords" prompt above the keyboard) rather than the Safari extension which provides suggestions that look like this:

That being said, we do have an iOS AutoFill biometric unlock internal issue open with our development team that matches that symptoms that you're reporting and I've added your comments there. Our developers will investigate this further.

Thanks again for taking the time to write in with your feedback. 🙂

-Dave

Thank you @1P_Dave - I just want to let you know that the last beta release does not fixed the problem. I just saw in the release notes that you did something with this update.

Looking forward for a fix.

@BKrnk

Thanks for following up. The issue that I mentioned in my earlier reply is still open with our development team. Hopefully a fix comes in a future update. 🙂

-Dave

ref: dev/core/core#17593

I hope have a fix soon :)

Keep me updated @1P_Dave

@BKrnk

When, and if, a fix is included in a future update you'll see it noted in our release notes: 1Password Releases

I'll also leave a note to circle back and update this thread.🙂

-Dave

@BKrnk

We've made some improvements to how haptics work when unlocking 1Password for iOS. Can you update to the latest version and let me know if you can still reproduce the issue:

• How to keep 1Password up to date

After updating, you might run into the problem one more time. But try to use AutoFill to fill a login again and let me know if you still experience the haptic issue.

-Dave

Unfortunately it still has a failure in there. The haptics on success are removed but this acts like it attempts an immediate retry on failure. So I can reproduce the haptic failure about 25 percent of the time on the newly released version.

1Password for iOS 8.10.24 81024044, on PRODUCTION channel

@linuxpng

Thanks for the reply. It sounds like you're referring to a slightly different issues that we're discussing in another thread.

Let's continue the conversation there. 🙂

-Dave