No notification or guidance when browser extension requests biometric unlock integration with non-App Store macOS desktop app

[chetanyb]

Steps To Reproduce

1. Install the Bitwarden macOS desktop app (not from the Mac App Store; e.g., direct download from Bitwarden website).
2. Install the Bitwarden browser extension from Firefox add-ons(tested on Waterfox, version 6.6.3, extension version 2025.9.0).
3. In the browser extension settings, enable 'Unlock with biometrics.'
4. The browser extension displays an 'Awaiting confirmation from desktop' popup (see screenshot below).
5. On the desktop app, there is no notification, popup, or guidance about what to do.
6. Manually navigate to the desktop app's settings > 'Allow browser integration' and attempt to enable it.
7. Only at this point does the desktop app inform the user stating 'Browser integration not supported: only supported in the Mac App Store version.' (see screenshot below)

Expected Result

The desktop app should immediately notify the user (via popup or in-app notification) that browser integration is not supported in the non-App Store version as soon as a browser extension requests biometric unlock. The browser extension and/or desktop app should provide clear guidance about the requirement to use the Mac App Store version for biometric integration.

Actual Result

The browser extension is stuck 'awaiting confirmation from desktop' with no progress or error. The desktop app gives no notification or prompt unless the user manually finds and clicks the browser integration checkbox in settings. No indication is provided about the Mac App Store requirement until the user stumbles upon the relevant setting.

Screenshots or Videos

Extension pop-up:

---

On manually enabling browser integration in desktop client app:

Additional Context

Bitwarden Mac client: Version 2025.9.0
SDK: 'main (ab3c7db)'
Shell: 36.8.1
Renderer: 136.0.7103.177
Node: 22.18.0
Architecture: arm64
Browser: Waterfox 6.6.3 (aarch64)
Extension: 2025.9.0
Server version: 2025.9.2
This is a UX issue, not a functional bug: the user is left without guidance, causing confusion and wasted troubleshooting.

Operating System

macOS

Operating System Version

Tahoe 26.0.1 (25A362), arm64

Web Browser

Firefox

Browser Version

6.6.3 (aarch64)

Environment Versions

Version: 2025.9.0

SDK: 'main (ab3c7db)'

Server version: 2025.9.2

Issue Tracking Info

• I understand that work is tracked outside of Github. A PR will be linked to this issue should one be opened to address it, but Bitwarden doesn't use fields like "assigned", "milestone", or "project" to track progress.

[bitwarden-bot]

Thank you for reporting this issue! We've added this to our internal tracking system.
ID: PM-26825
Link (for internal use): https://bitwarden.atlassian.net/browse/PM-26825

[pamperer562580892423]

Another user here. And though I can understand your point, this only happens to users who don't read the documentation... https://bitwarden.com/help/biometrics/ ... Second sentence in the "MacOS" tab mentions this already: https://bitwarden.com/help/biometrics/#tab-macos-2vCWb5iFg4OqKS0B2xXpqW

And when you miss that in the Help Sites, the desktop app notifies you when you try to activate "Allow browser integration", when you followed the rest of the documentation.

[chetanyb]

Another user here. And though I can understand your point, this only happens to users who don't read the documentation... https://bitwarden.com/help/biometrics/ ... Second sentence in the "MacOS" tab mentions this already: https://bitwarden.com/help/biometrics/#tab-macos-2vCWb5iFg4OqKS0B2xXpqW

And when you miss that in the Help Sites, the desktop app notifies you when you try to activate "Allow browser integration", when you followed the rest of the documentation.

@pamperer562580892423 thanks for your input and for sharing the documentation link!
I would restate—the issue here is primarily about user experience, not user error. Even when documentation exists, most users expect in-app guidance, especially when a feature fails silently or gives an unclear message like "Awaiting confirmation from desktop."

A simple redirect to the help page you shared, or a clear notification explaining why the integration isn't possible, would prevent confusion for all users, regardless of whether they've read the documentation. This is a standard UX best practice and would make the experience smoother for everyone.

Thanks again for contributing to the discussion!