EDIT: Below is wrong, sorry. Security keys both for standalone 2FA and with Passkeys are working on my Intel Thinkpad. So maybe this is a ARM Mac issue as others have said.

Same issue on a Thinkpad X280 running Fedora Linux 40 under Wayland.
Tried with multiple logins: Google, Bitwarden, GitHub.
Zen installed from Flatpak. Zen version: 1.0.0-a.27 (fresh install today)
Tried two Yubikeys: USB-A and USB-C.
USB access is not the problem as Zen can see a USB flash drive and Flatseal shows device=all permission.
Firefox on this machine is able to access USB security keys fine.

It's the same issue with this. Looks like they closed it saying that maybe it's on the Firefox side but according to the last comment there it looks like it's not the case. I hope they look into that I'm having the same issue on every website with Passkey authentication.

#111

I'll try looking into this

+1

I just drop this here as it wasn't mentioned before. This might be related to not having this entitlement.

I'm not sure how easy it is to add that or if the app needs to pay the gatekeeper fee for proper signing.

I just drop this here as it wasn't mentioned before. This might be related to not having this entitlement.

I'm not sure how easy it is to add that or if the app needs to pay the gatekeeper fee for proper signing.

You won't believe what comment I just left on the other issue because I forgot to read this one as well first 🤦

Either way, from what I can tell just paying the gatekeeper fee alone isn't gonna cut it, this is an additional entitlement unfortunately. I'm not sure how likely Apple is to give it out either, since they haven't done so for the other browsers I mentioned in the other issue (though that said, those browsers may not even have tried to apply either)

I'm also having this issue, but its when I try to log back into my 1password plugin from Zen using the touch id instead of having to retype the password.
I have the plugin in my firefox browser and its working just fine, so i don't think its a firefox side issue.

Edit: also this is from a 2019 Macbook Pro w/ Intel chip, running macOS Version 15.0 Beta (24A5298h)

I have 3 1Password accounts I log into separately but Touch ID manages that for me. Due to this bug, I can only use one of them at a time. This is unfortunately a blocker for me to use Zen Browser on my work computer, otherwise I love it.

Update: macos has been signed! Let's wait for version 38 to build, and see if this issue goes away or 1password accepts zen or whatever

Just to clarify @mauro-balades, what are we waiting on to get this resolved? I understood your comment above as "v38 will support passkeys," but I've tried the v39 alpha and it still doesn't seem to be working. If it's not been fixed due to a lack of human resources, is it something we could perhaps delegate to the community? I'd love to help out and expedite this if I can (for my own sake! 😄)

I understand this is OSS and your time is very precious, so thank you for your hard work.

18-Sep-2024 10:36 GMT+8

Passkeys functionality on Mac still not available.
Currently using 1.0.1-a.1

I can confirm that as of 24 September 2024, it is still not working on ARM macbooks.
Currently using 1.0.1-a.4 (64-bit)

Version: 1.0.1-a.7 (64-bit)
Date: 2 Oct 2024
Issues: Passkey options is not rendered on some login pages and on Github I get this message:

On google it is still the same issue with the ARM macbook closed:

This is the only issue that is stopping me from using Zen browser for now. Will stick to firefox

Same issue for me, cannot use my yubikey as a 2fa. I can't even click the cancel button, it freezes after i click it

What does firefox do?

What does firefox do?

Nvm, it's borked in firefox also, i remember it working a few updates back. Basically it let u click the 2fa key and it'd proceed to login, now it just hangs

What does firefox do?

Nvm, it's borked in firefox also, i remember it working a few updates back. Basically it let u click the 2fa key and it'd proceed to login, now it just hangs

It lets me use passkey:

(I didn't upload whole screenshot because of sensitive data and I am lazy to blur it)

• 1.0.1-a.9
• Macbook M-series
• 15 Oct 2024

Can confirm, passkey still wont work.

Still occurs even after doing the followin

• Complete removal and reinstallation of Zen
• Sync and unsync of account (i don't know why I did this XD)
• System reboot

Still not work

yes, just tested on 1.0.1-a.12 (Firefox 131.0.3) (aarch64) still doesn't work (login google.com)

And today was the first time my passkey with gmail worked!

And today was the first time my passkey with gmail worked!

It still doesn't work on: 1.0.1-a.17 (Firefox 132.0) (aarch64)

Guys, I understand, but please don't write any comments that dont positively contribute to the issue "logically?". Because everyone subscribed gets a notification when you comment.

Im still working on this issue, you can follow the progress here:

#4601

I had to rewrite the codesign process so we now use Firefox's built in one, this will hopefully finally give us access to this feature

No I'm not using mac os, I added the info that I'm using Linux 98 seconds after I wrote the message. Why disliking it immediately?

I'm just trying a new thing. I don't even know if some other popup supposed to be shown to select a device like my phone or not. And I don't know if it's a bug or there's just no such feature like using phone over Bluetooth as a passkey device.

UPD seems like there's just no such feature even in firefox 😿

@nikelborm This thread is specifically about macOS, so you would be better off posting a new issue (assuming there's not one specific to Linux yet). Maybe we should update the issue name to prevent confusion...

You have reactions because there are probably around a hundred or a few hundred people subscribed to this waiting for constructive updates because it's important for them, and we all getting spammed almost daily with emails with zero constructive info on the topic, which makes whole subscription useless and annoying. It's just accumulated tiredness for over 50 comments essentially asking the same rhethoric "when" question, especially after developer response asking specifically to stop doing that and the OP problem is worked on. Yes, even if your question is different, it is stated in OP that it concerns a specific feature on a specific platform.

Please don't take it personally, and I would really ask everyone to consider whether their response contributes anything to the resolution of this topic.

I think @mauro-balades is already working on resolving it. Check PRs #4601 and #4790 . I am waiting for the Twilight to test. Thanks @mauro-balades for the effort

Just to add +1 to the statistics

I think this does nothing to help; the issue already has 112 thumbs ups and I think the maintainers are aware of it. Also, people are subscribed to this issue to see progress and getting spammed by comments like this.
This isn't targeted at your specific comment, but all "bump" comments.

tldr: stop spamming

1. I don’t know the project maintainers’ intended use of GitHub issues is, but issues was originally designed as a bug tracker and not customer support, and most definitely not a forum. If you want to comment something, please make sure it directly helps with solving the issue itself. Useless messages are just wasting the maintainers’ limited time and attention.
2. Whenever someone sends something here, EVERYONE subscribed to the issue hoping to get useful information gets a spam (like this message itself would too, and I hope this is the last time it’s going to happen here). Please be considerate and not spam everyone. Reach with a thumbs up on the original post should be enough.
3. Idk what allows you to take feature requests for granted, especially when you’re using the product for free while the maintainer is out of their own pocket doing the project for passion. Only the project maintainer has a say on how they do their project, not you. Idk, being polite sounds like a basic and obvious manner to me.
4. It is really easy to find the pull request trying to solve this issue. Please at least spend minimal effort of searching before doing any of this. (And no, that doesn’t mean not having an open PR allows you to spam here)
5. I myself am not a maintainer and I’m not trying to act like one. I’m just writing what the general expectations are from GitHub issues that is somehow not immediately obvious to a bunch of ppl.

We are tired of waiting for such a small but necessary feature. - rayrnond

I am more tired of spam messages (yours and many others’), and I think I’m unsubscribing from this thread.

Edit: Okay wtf… ppl really don’t know how to read or something it’s driving me insane…

@mauro-balades or other maintainers, would you please lock this issue's comments?

This conversation is absolutely pointless.