Wayland browser extension login issue

The browser extension prompting for your 1Password credentials indicates that it's not communicating with the local client (via the socket), but to 1Password's service. Since your browser can connect to the socket, it sounds like it's not resulting in the client launching and displaying the 1Password is trying to unlock the browser extension window which prompts for the password.

I've not tested on an Arch platform recently.

Do you have the 1password client installed from AUR and if so, then which package?

PS. Your post title starts with "Wayland browser", but it's unclear how Wayland is relevant.

I'm running this one from the AUR: https://aur.archlinux.org/packages/1password

The Wayland was just for more information, in case it is one of those issues that works under xorg but not wayland. I've seen that with display issues on other apps. 

And from some experimenting, the field to enter the password is there, it just isn't visible. 

I'll add as I'm in the same boat.

I'm using Arch with Gnome on Wayland (started with Hyprland as well). I've installed the AUR package (https://aur.archlinux.org/packages/1password) and using the Firefox extension on Zen browser. Because the extension and app are not synci

ng, I have to login to both to do anything.

Settings on the browser

Settings on the app

Toggling either on/off shows no difference in behaviour and the app logs show no updates when I toggle the setting in the extension. This tells me the extension does not recognize the socket for the app.

If I search for open sockets, I see it's created. (hash codes and user ids hidden)

> ss -a | grep 1Password
u_str LISTEN     0      0  /run/user/$UID/1Password-BrowserSupport.sock 4542562    * 0     
u_seq LISTEN     0      0              @/tmp/1Password-$UID/_hash_code_ 4534994    * 0     
u_seq ESTAB      0      0              @/tmp/1Password-$UID/_hash_code_ 4534995    * 0