github-starred/android
2
0
Fork 0
mirror of https://github.com/bitwarden/android.git synced 2026-05-08 12:58:36 -05:00
Code Issues 1.1k Packages Projects Releases 122 Wiki Activity

[GH-ISSUE #5189] Option to enable biometric unlock is missing on Work Profile when One Lock is enabled #21487

New Issue
Closed
opened 2026-04-16 22:00:06 -05:00 by GiteaMirror · 4 comments
GiteaMirror commented 2026-04-16 22:00:06 -05:00
Owner
Copy Link

Originally created by @mattjago on GitHub (May 14, 2025).
Original GitHub issue: https://github.com/bitwarden/android/issues/5189

Steps To Reproduce

1 Enable a Work profile on your android device
2 In your device settings go to Security and Privacy -> More Settings and Privacy-> Turn on 'Use one lock'
(steps taken from a Pixel 9 Pro Fold, may differ on other devices)
3 Install Bitwarden on the Work Profile and sign in with master password
4 Go to Settings in the Bitwarden app and find that the option to enable biometric unlock is not present

Expected Result

Expect to be able to enable biometric unlock for the bitwarden app.

Actual Result

No option to enable biometric unlock is present.

Screenshots or Videos

No response

Additional Context

Android provides the ability to have separate device security (pin/fingerprint/face unlock) for main vs work profiles or to enable One Lock which allows the same security to be used across both main and work profiles.
When One Lock is disabled and distinct device biometrics are setup for different profiles the option to enable biometric unlock is available in the bitwarden app. But with one lock enabled, the biometric unlock is only available in the 'main profile' instance of bitwarden, not the the 'work profile' instance.

Build Version

2025.4.0

What server are you connecting to?

EU

Self-host Server Version

No response

Environment Details

Device: Pixel 9 Pro Fold
Android 15 - May Security Patch

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.
Originally created by @mattjago on GitHub (May 14, 2025). Original GitHub issue: https://github.com/bitwarden/android/issues/5189 ### Steps To Reproduce 1 Enable a Work profile on your android device 2 In your device settings go to Security and Privacy -> More Settings and Privacy-> Turn on 'Use one lock' (steps taken from a Pixel 9 Pro Fold, may differ on other devices) 3 Install Bitwarden on the Work Profile and sign in with master password 4 Go to Settings in the Bitwarden app and find that the option to enable biometric unlock is not present ### Expected Result Expect to be able to enable biometric unlock for the bitwarden app. ### Actual Result No option to enable biometric unlock is present. ### Screenshots or Videos _No response_ ### Additional Context Android provides the ability to have separate device security (pin/fingerprint/face unlock) for main vs work profiles or to enable One Lock which allows the same security to be used across both main and work profiles. When One Lock is disabled and distinct device biometrics are setup for different profiles the option to enable biometric unlock is available in the bitwarden app. But with one lock enabled, the biometric unlock is only available in the 'main profile' instance of bitwarden, not the the 'work profile' instance. ### Build Version 2025.4.0 ### What server are you connecting to? EU ### Self-host Server Version _No response_ ### Environment Details Device: Pixel 9 Pro Fold Android 15 - May Security Patch ### Issue Tracking Info - [x] 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.
GiteaMirror added the app:password-managerbug labels 2026-04-16 22:00:06 -05:00
GiteaMirror commented 2026-04-16 22:00:07 -05:00
Author
Owner
Copy Link

@bitwarden-bot commented on GitHub (May 14, 2025):

Thank you for your report! We've added this to our internal board for review.
ID: PM-21619

<!-- gh-comment-id:2880522024 --> @bitwarden-bot commented on GitHub (May 14, 2025): Thank you for your report! We've added this to our internal board for review. ID: PM-21619
GiteaMirror commented 2026-04-16 22:00:08 -05:00
Author
Owner
Copy Link

@closebot-bw commented on GitHub (Feb 11, 2026):

⚠️ Stale Issue Notice

This issue has been automatically marked as stale due to inactivity. It will be closed in 2 weeks (February 25, 2026) if no further activity occurs.

If this issue is still relevant and you would like to keep it open, please:

  • Comment on this issue to show continued interest
  • Provide any additional information or updates
  • Confirm that the issue still exists in the latest version

Thank you for your contribution to this project! 🙏

<!-- gh-comment-id:3886596217 --> @closebot-bw commented on GitHub (Feb 11, 2026): ⚠️ **Stale Issue Notice** This issue has been automatically marked as stale due to inactivity. It will be closed in **2 weeks** (February 25, 2026) if no further activity occurs. If this issue is still relevant and you would like to keep it open, please: - Comment on this issue to show continued interest - Provide any additional information or updates - Confirm that the issue still exists in the latest version Thank you for your contribution to this project! 🙏
GiteaMirror commented 2026-04-16 22:00:08 -05:00
Author
Owner
Copy Link

@closebot-bw commented on GitHub (Feb 23, 2026):

🔔 Final Notice - Issue Will Be Closed Soon

This issue was previously marked as stale and will be automatically closed in 2 days (February 25, 2026) if no further activity occurs.

If you're still experiencing this issue or believe it should remain open, please comment below to prevent automatic closure.

We appreciate your understanding and contribution to keeping our issue tracker organized! 📋

<!-- gh-comment-id:3946973011 --> @closebot-bw commented on GitHub (Feb 23, 2026): 🔔 **Final Notice - Issue Will Be Closed Soon** This issue was previously marked as stale and will be automatically closed in **2 days** (February 25, 2026) if no further activity occurs. If you're still experiencing this issue or believe it should remain open, please comment below to prevent automatic closure. We appreciate your understanding and contribution to keeping our issue tracker organized! 📋
GiteaMirror commented 2026-04-16 22:00:08 -05:00
Author
Owner
Copy Link

@closebot-bw commented on GitHub (Feb 25, 2026):

🔒 Issue Closed Due to Inactivity

This issue has been automatically closed due to lack of activity for an extended period. We periodically review and close inactive issues to help maintain our issue tracker and focus on current priorities.

If this issue is still relevant:

  • Please create a new issue with updated information
  • Include steps to reproduce the problem if it's a bug report
  • Mention if this issue still occurs in the latest version

Thank you for your contribution to this project. Your feedback helps us improve! 🙏

<!-- gh-comment-id:3961979638 --> @closebot-bw commented on GitHub (Feb 25, 2026): 🔒 **Issue Closed Due to Inactivity** This issue has been automatically closed due to lack of activity for an extended period. We periodically review and close inactive issues to help maintain our issue tracker and focus on current priorities. **If this issue is still relevant:** - Please create a new issue with updated information - Include steps to reproduce the problem if it's a bug report - Mention if this issue still occurs in the latest version Thank you for your contribution to this project. Your feedback helps us improve! 🙏
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
app:authenticator
app:password-manager
bug
bug-passkey
customer-support
duplicate
enhancement
good first issue
help wanted
needs-reply
needs-response
pull-request
Mirrored from GitHub Pull Request
 question
No Label app:password-manager bug
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/android#21487
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?