Casey LissIt'll be better, they said! 1Password 8 is our best yet*.
* = for us. For the customer, it's tale of 1000 papercuts.
Update: I disabled and re-enabled the Safari extension. It now shows the extension... but won't autofill.
🥴
Michael Fey 
@caseyliss @1password For Pete’s sake. So sorry dude.
@MrRooni with respect, I hope 1Password 8 has been spectacular for y’all. Because for me, it’s been the opposite.
The problem with setting such a high bar with 7 is that it makes it hurt that much more when 8 misses the mark.
@caseyliss You’re not alone in your experience and we’re working to make it better. I realize that doesn’t help in the moment.
@MrRooni I was prompted to TouchID seconds before this. Once I did, everything disappeared, and now I see this.
I really don't mean to beat a dead horse here, but truly, 1P8 is an exercise in papercuts.
@MrRooni Oh fun. 🙄
@MrRooni The other really shitty part is, these issues may very well be with Safari. And in 1P7, everything was so rock-solid, that I'd have blamed Safari first.
But now, my natural assumption is that it’s 1P8's fault, because so many things are broken in small and insufferable ways these days.
Y'all have bought internal speed/ease of development by spending my confidence and enthusiasm.
@MrRooni Aaaaaaaand just found myself in this infinite loop again.
@caseyliss A possible workaround is to use Universal Autofill instead. It doesn’t use the browser extension at all and instead uses the macOS accessibility APIs to fill your credentials. By default it can be invoked with Command + \. https://support.1password.com/mac-universal-autofill/
@MrRooni This time was iPad though.
@caseyliss Goddammit. Password AutoFill is still great for usernames and passwords, but not for credit cards and personal info. You could drag and drop from the main app in slide over. (I realize that the extension should work, but at this point I’m doing triage until we can get it sorted for you).