github-starred/android
2
0
Fork 0
mirror of https://github.com/bitwarden/android.git synced 2026-05-07 19:39:41 -05:00
Code Issues 1.1k Packages Projects Releases 122 Wiki Activity

[GH-ISSUE #4962] Biometrics fail to enable when installed inside Android Work Profile #39172

New Issue
Open
opened 2026-04-23 17:50:46 -05:00 by GiteaMirror · 8 comments
GiteaMirror commented 2026-04-23 17:50:46 -05:00
Owner
Copy Link

Originally created by @jstorrs on GitHub (Apr 2, 2025).
Original GitHub issue: https://github.com/bitwarden/android/issues/4962

Steps To Reproduce

  1. Create an Android Work Profile (see additional context)
  2. Install Bitwarden inside the Work Profile
  3. Open Bitwarden, login open vault
  4. Go to Settings > Account security
  5. Click "Unlock with Biometrics" toggle to enable

Expected Result

Expected result is that biometrics is enabled.

Actual Result

Biometrics fails to enable with the message: "An error has occurred." "We were unable to process your request. Please try again or contact us."

Screenshots or Videos

No response

Additional Context

This is related to Android's Work Profile feature which is used to isolate work-related apps. With Work Profile the phone essentially has two different users are logged in simultaneously, the Main Profile and the Work Profile, each with separate groups of apps. Apps in both profiles can be used simultaneously they are essentially sandboxed from each other (each has their own instance of Play Store etc).

https://support.google.com/work/android/answer/6191949?hl=en

When Bitwarden is only installed in the Main Profile, then Work Profile does not have access to the Main Profile Bitwarden autofill. To get autofill working in Work Profile you install Bitwarden in Work Profile, also. After this, Bitwarden works as expected for Work Profile apps; however, the Work Profile Bitwarden is not able to enable biometrics for some reason.

Other apps seem able to enable biometrics when installed simultaneously in Main Profile and Work Profile (tested example: Microsoft Authenticator).

To create a Work Profile if your employer/whatever doesn't support the feature, one way to test is to bootstrap the initial Work Profile is using the Shelter app. https://github.com/PeterCxy/Shelter (also available on F-Droid) After the Work Profile is setup then use Work Profile Play Store to log in to a Google Account (requires an account that is not already used in the device's Main Profile) and then install Bitwarden. Note: Shelter is able to copy apps from Main Profile to Work Profile, but I'm not sure whether or how updates to those apps happen. For Work Profile apps generally install from Play Store seems needed to install apps required by your employer (Outlook, etc).

Build Version

2025.2.0 (19883)

What server are you connecting to?

US

Self-host Server Version

No response

Environment Details

  • Device: Google Pixel 7
  • Android 15 (March 5, 2025 security update)
  • Google Play (Jan 1, 2025)
  • Build number: BP1A.250305.019

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 @jstorrs on GitHub (Apr 2, 2025). Original GitHub issue: https://github.com/bitwarden/android/issues/4962 ### Steps To Reproduce 1. Create an Android Work Profile (see additional context) 2. Install Bitwarden inside the Work Profile 3. Open Bitwarden, login open vault 4. Go to Settings > Account security 5. Click "Unlock with Biometrics" toggle to enable ### Expected Result Expected result is that biometrics is enabled. ### Actual Result Biometrics fails to enable with the message: "An error has occurred." "We were unable to process your request. Please try again or contact us." ### Screenshots or Videos _No response_ ### Additional Context This is related to Android's Work Profile feature which is used to isolate work-related apps. With Work Profile the phone essentially has two different users are logged in simultaneously, the Main Profile and the Work Profile, each with separate groups of apps. Apps in both profiles can be used simultaneously they are essentially sandboxed from each other (each has their own instance of Play Store etc). https://support.google.com/work/android/answer/6191949?hl=en When Bitwarden is only installed in the Main Profile, then Work Profile does not have access to the Main Profile Bitwarden autofill. To get autofill working in Work Profile you install Bitwarden in Work Profile, also. After this, Bitwarden works as expected for Work Profile apps; however, the Work Profile Bitwarden is not able to enable biometrics for some reason. Other apps seem able to enable biometrics when installed simultaneously in Main Profile and Work Profile (tested example: Microsoft Authenticator). To create a Work Profile if your employer/whatever doesn't support the feature, one way to test is to bootstrap the initial Work Profile is using the Shelter app. https://github.com/PeterCxy/Shelter (also available on F-Droid) After the Work Profile is setup then use Work Profile Play Store to log in to a Google Account (requires an account that is not already used in the device's Main Profile) and then install Bitwarden. Note: Shelter is able to copy apps from Main Profile to Work Profile, but I'm not sure whether or how updates to those apps happen. For Work Profile apps generally install from Play Store seems needed to install apps required by your employer (Outlook, etc). ### Build Version 2025.2.0 (19883) ### What server are you connecting to? US ### Self-host Server Version _No response_ ### Environment Details - Device: Google Pixel 7 - Android 15 (March 5, 2025 security update) - Google Play (Jan 1, 2025) - Build number: BP1A.250305.019 ### 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 bugapp:password-manager labels 2026-04-23 17:50:46 -05:00
GiteaMirror commented 2026-04-23 17:50:48 -05:00
Author
Owner
Copy Link

@S-Kakar commented on GitHub (Apr 2, 2025):

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

<!-- gh-comment-id:2772489220 --> @S-Kakar commented on GitHub (Apr 2, 2025): Thank you for your report! We've added this to our internal board for review. ID: PM-19802
GiteaMirror commented 2026-04-23 17:50:49 -05:00
Author
Owner
Copy Link

@Krychaz commented on GitHub (Apr 3, 2025):

Hello there,

It sounds like your issue could be related to this overall issue with Biometric and Android Work Profile - https://github.com/bitwarden/android/issues/4659

<!-- gh-comment-id:2775655209 --> @Krychaz commented on GitHub (Apr 3, 2025): Hello there, It sounds like your issue could be related to this overall issue with Biometric and Android Work Profile - https://github.com/bitwarden/android/issues/4659
GiteaMirror commented 2026-04-23 17:50:51 -05:00
Author
Owner
Copy Link

@jstorrs commented on GitHub (Apr 3, 2025):

I read that bug report after submitting this one and it inspired a test on my end.

The bug you referenced is talking about two different Bitwarden accounts used simultaneously in the same Bitwarden app. This is about having two copies of Bitwarden app installed and in use simultaneously using the Android Work Profile feature. One copy is the Main Profile Bitwarden and the other copy is the Work Profile Bitwarden. Android makes sure each of these copies has no idea the other exists. They both show up in the app list, but one has a small briefcase in the bottom right corner to mark it as Work Profile.

Nevertheless after reading that bug it seemed reasonable that it might have something to do with how the secure element is accessed and that something at the lower levels might not be able to tell the difference between accounts/apps/etc. So, I tried disabling biometrics in my Main Profile bitwarden to see if that would allow the Work Profile bitwarden to enable biometrics. But nothing changed. Work Profile still gives the same error and Main Profile us able to re-enable biometrics.

Just to reiterate that bug isn't talking about Android Work Profile at all. When I searched the open/closed issues for other Work Profile bugs I found some that were closed because the users found clumsy workarounds and it didn't seem like the developers understood what Android Work Profile is.

Another difference is that I am actually using the same Bitwarden account both in Main Profile and Work Profile instances of Bitwarden app (which is not possible in a single instance of Bitwarden app)

I'll try to get adb logs in the next few days to see if it's the same code path.

Also, I'm not seeing a crash. Just the error message and failure to enable biometrics.

<!-- gh-comment-id:2775715944 --> @jstorrs commented on GitHub (Apr 3, 2025): I read that bug report after submitting this one and it inspired a test on my end. The bug you referenced is talking about two different Bitwarden accounts used simultaneously in the same Bitwarden app. This is about having two copies of Bitwarden app installed and in use simultaneously using the Android Work Profile feature. One copy is the Main Profile Bitwarden and the other copy is the Work Profile Bitwarden. Android makes sure each of these copies has no idea the other exists. They both show up in the app list, but one has a small briefcase in the bottom right corner to mark it as Work Profile. Nevertheless after reading that bug it seemed reasonable that it might have something to do with how the secure element is accessed and that something at the lower levels might not be able to tell the difference between accounts/apps/etc. So, I tried disabling biometrics in my Main Profile bitwarden to see if that would allow the Work Profile bitwarden to enable biometrics. But nothing changed. Work Profile still gives the same error and Main Profile us able to re-enable biometrics. Just to reiterate that bug isn't talking about Android Work Profile at all. When I searched the open/closed issues for other Work Profile bugs I found some that were closed because the users found clumsy workarounds and it didn't seem like the developers understood what Android Work Profile is. Another difference is that I am actually using the same Bitwarden account both in Main Profile and Work Profile instances of Bitwarden app (which is not possible in a single instance of Bitwarden app) I'll try to get adb logs in the next few days to see if it's the same code path. Also, I'm not seeing a crash. Just the error message and failure to enable biometrics.
GiteaMirror commented 2026-04-23 17:50:52 -05:00
Author
Owner
Copy Link

@jstorrs commented on GitHub (Apr 3, 2025):

After rereading that other bug, another difference is that they are able to enable biometrics and then crashes happen afterwards. I'm not able to actually get to the point of enabling it. The errors happen before.

When you enable biometrics, the next step is Android pops up a fingerprint confirmation. It seems the people in that other bug make it past that step. In my case I get the error message before the fingerprint confirmation ever pops up. So I am not able to enable biometrics in the Work Profile copy of Bitwarden app. I think that probably means it's a different location in the code that's failing for me. It could well be the same core handling of biometrics at play, though.

<!-- gh-comment-id:2775825439 --> @jstorrs commented on GitHub (Apr 3, 2025): After rereading that other bug, another difference is that they are able to enable biometrics and then crashes happen afterwards. I'm not able to actually get to the point of enabling it. The errors happen before. When you enable biometrics, the next step is Android pops up a fingerprint confirmation. It seems the people in that other bug make it past that step. In my case I get the error message before the fingerprint confirmation ever pops up. So I am not able to enable biometrics in the Work Profile copy of Bitwarden app. I think that probably means it's a different location in the code that's failing for me. It could well be the same core handling of biometrics at play, though.
GiteaMirror commented 2026-04-23 17:50:53 -05:00
Author
Owner
Copy Link

@ndesgranges commented on GitHub (Apr 25, 2025):

I've been commenting the other issue. There is more to this.
Some have the issue with 2 accounts
Some have issues with work profile

For my part, I do not even need a work profile for this to happens. it just crashes on enabling

So these could all be linked, or, maybe there are mutliple issues here.

<!-- gh-comment-id:2830338219 --> @ndesgranges commented on GitHub (Apr 25, 2025): I've been commenting [_the other issue_](https://github.com/bitwarden/android/issues/4659). There is more to this. Some have the issue with 2 accounts Some have issues with work profile For my part, I do not even need a work profile for this to happens. it just crashes on **enabling** So these could all be linked, or, maybe there are mutliple issues here.
GiteaMirror commented 2026-04-23 17:50:54 -05:00
Author
Owner
Copy Link

@igormcoelho commented on GitHub (Nov 11, 2025):

I experience a similar situation with work profile and bitwarden, since the option "Unlock with Biometrics" doesn't even appear on my work profile bitwarden, only in the main one. Another problem is that auto-fill services toggle does not turn on, even if I click it and gets "Bitwarden" selected from the system, then it continues to be off (maybe similar to this https://github.com/bitwarden/mobile/issues/427). I'm using Android 16 on Samsung Galaxy UI 8.0 with Shelter, did you really manage to make autofill work @jstorrs ? xD In my case, Bitwarden is only useful on the main profile, as nothing works on the work profile (autofill, PIN, biometrics, ...), so I guess it's tricky this work profile technology.

<!-- gh-comment-id:3518918247 --> @igormcoelho commented on GitHub (Nov 11, 2025): I experience a similar situation with work profile and bitwarden, since the option "Unlock with Biometrics" doesn't even appear on my work profile bitwarden, only in the main one. Another problem is that auto-fill services toggle does not turn on, even if I click it and gets "Bitwarden" selected from the system, then it continues to be off (maybe similar to this https://github.com/bitwarden/mobile/issues/427). I'm using Android 16 on Samsung Galaxy UI 8.0 with Shelter, did you really manage to make autofill work @jstorrs ? xD In my case, Bitwarden is only useful on the main profile, as nothing works on the work profile (autofill, PIN, biometrics, ...), so I guess it's tricky this work profile technology.
GiteaMirror commented 2026-04-23 17:50:56 -05:00
Author
Owner
Copy Link

@jstorrs commented on GitHub (Nov 11, 2025):

Yes, it's all working fine. The biometrics ended up being something I hadn't considered--you have to enable biometrics and register fingers and faces separately for the work profile in Android settings... You also have to configure autofill in the work profile separately. It doesn't share preferences or fingers with the main profile. On Android 16 (can't remember how it worked on 15):

Settings > Security and Privacy > "Device unlock" has "Fingerprint", "Fingerprint for work", "Face" and "Face for work"

Settings > "Passwords, passkeys & accounts" has "Personal" and "Work" tabs

I don't think the problem is in bitwarden. Android Work profile just doesn't have great feedback about biometrics and autofill not working and it's easy to trick yourself into thinking it's the app and not android settings for the profile. Anyway it took me embarrassingly long for it to fully sink in that Work and Personal are completely different accounts and isolated from each other.

<!-- gh-comment-id:3519028487 --> @jstorrs commented on GitHub (Nov 11, 2025): Yes, it's all working fine. The biometrics ended up being something I hadn't considered--you have to enable biometrics and register fingers and faces separately for the work profile in Android settings... You also have to configure autofill in the work profile separately. It doesn't share preferences or fingers with the main profile. On Android 16 (can't remember how it worked on 15): Settings > Security and Privacy > "Device unlock" has "Fingerprint", "Fingerprint for work", "Face" and "Face for work" Settings > "Passwords, passkeys & accounts" has "Personal" and "Work" tabs I don't think the problem is in bitwarden. Android Work profile just doesn't have great feedback about biometrics and autofill not working and it's easy to trick yourself into thinking it's the app and not android settings for the profile. Anyway it took me embarrassingly long for it to fully sink in that Work and Personal are completely different accounts and isolated from each other.
GiteaMirror commented 2026-04-23 17:50:57 -05:00
Author
Owner
Copy Link

@igormcoelho commented on GitHub (Nov 11, 2025):

Thanks A LOT @jstorrs ! It worked both configurations! In my case, it's all in portuguese, so it's even harder to find the correct translations xD
My biometrics was not appearing on bitwarden for work profile because I really didn't have one (for work profile)... after creating one, following your instructions, it worked!
Then, the autofill I followed your advice as well... A small fix to your valuable answer, at least in my case: Settings > Security and Privacy -> More security configurations -> "Passwords, passkeys & accounts" has "Personal" and "Work" tabs
And the other one: Settings > Security and Privacy -> More security configurations -> Security for Work Profile -> then add fingerprints and face (for work profile).
Maybe it's the adapted Samsung UI, I don't know, but at least I found them now, and it's all working fine!

So, my only advice here (for bitwarden app) is that when setting Bitwarden on work profile for auto-fill, it will redirect you to the Auto-fill option for Main Profile, not the correct one on the Work Profile... but it could be hard or impossible for the app to know where to point to, unless it knew it was a Work Profile app :) So, that's fine to be done manually, all fixed and working perfectly.
Regards!

<!-- gh-comment-id:3519093543 --> @igormcoelho commented on GitHub (Nov 11, 2025): Thanks A LOT @jstorrs ! It worked both configurations! In my case, it's all in portuguese, so it's even harder to find the correct translations xD My biometrics was not appearing on bitwarden for work profile because I really didn't have one (for work profile)... after creating one, following your instructions, it worked! Then, the autofill I followed your advice as well... A small fix to your valuable answer, at least in my case: Settings > **Security and Privacy** -> **More security configurations** -> "Passwords, passkeys & accounts" has "Personal" and "Work" tabs And the other one: Settings > **Security and Privacy** -> **More security configurations** -> **Security for Work Profile** -> then add fingerprints and face (for work profile). Maybe it's the adapted Samsung UI, I don't know, but at least I found them now, and it's all working fine! So, my only advice here (for bitwarden app) is that when setting Bitwarden on work profile for auto-fill, it will redirect you to the Auto-fill option for Main Profile, not the correct one on the Work Profile... but it could be hard or impossible for the app to know where to point to, unless it knew it was a Work Profile app :) So, that's fine to be done manually, all fixed and working perfectly. Regards!
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#39172
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?