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

[GH-ISSUE #5814] [PM-25367] Using mobile to authorize desktop logins does bring me directly to the authorize screen #21600

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

Originally created by @endlessterror on GitHub (Sep 2, 2025).
Original GitHub issue: https://github.com/bitwarden/android/issues/5814

Steps To Reproduce

  1. Configure mobile to unlock with fingerprint (that's my setup)
  2. Configure say the firefox extension to unlock via mobile authorization
  3. Logout from firefox BW extension
  4. Login to BW firefox extension, you'll be asked to provide the email. Do so
  5. In the next step select to login using a device
  6. On my android device a notification pops up to confirm my connection request
  7. Press on the notification request pop up. The verification will be shown full screen in the background, including the verification phrase, while in the foreground the fingerprint dialog will be shown.
  8. Tap the fingerprint to unlock

Expected Result

The overlay goes away and I press the confirm button for the verification

Actual Result

The overlay goes away, but I'm switched to the main BW panel. I have to select settings -> account security -> pending account requests -> (the current request) -> and THEN press the confirm button for the verification

Screenshots or Videos

No response

Additional Context

No response

Build Version

2025.8.0

What server are you connecting to?

EU

Self-host Server Version

No response

Environment Details

  • Samsung S21+
  • Android 15

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 @endlessterror on GitHub (Sep 2, 2025). Original GitHub issue: https://github.com/bitwarden/android/issues/5814 ### Steps To Reproduce 1. Configure mobile to unlock with fingerprint (that's my setup) 2. Configure say the firefox extension to unlock via mobile authorization 3. Logout from firefox BW extension 4. Login to BW firefox extension, you'll be asked to provide the email. Do so 5. In the next step select to login using a device 6. On my android device a notification pops up to confirm my connection request 7. Press on the notification request pop up. The verification will be shown full screen in the background, including the verification phrase, while in the foreground the fingerprint dialog will be shown. 8. Tap the fingerprint to unlock ### Expected Result The overlay goes away and I press the confirm button for the verification ### Actual Result The overlay goes away, but I'm switched to the main BW panel. I have to select settings -> account security -> pending account requests -> (the current request) -> and THEN press the confirm button for the verification ### Screenshots or Videos _No response_ ### Additional Context _No response_ ### Build Version 2025.8.0 ### What server are you connecting to? EU ### Self-host Server Version _No response_ ### Environment Details - Samsung S21+ - Android 15 ### 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:09:43 -05:00
GiteaMirror commented 2026-04-16 22:09:46 -05:00
Author
Owner
Copy Link

@bitwarden-bot commented on GitHub (Sep 2, 2025):

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

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

@pamperer562580892423 commented on GitHub (Sep 2, 2025):

Another user here.

It sounds to me like this could be related to this issue: https://github.com/bitwarden/android/issues/5777

<!-- gh-comment-id:3245705696 --> @pamperer562580892423 commented on GitHub (Sep 2, 2025): Another user here. It sounds to me like this could be related to this issue: https://github.com/bitwarden/android/issues/5777
GiteaMirror commented 2026-04-16 22:09:47 -05:00
Author
Owner
Copy Link

@daniellbw commented on GitHub (Sep 5, 2025):

Hi there,

Thank you for your report!

I was able to reproduce this issue, and I have flagged this to our engineering team. As mentioned by @pamperer562580892423 this might be related to #5777

If you wish to add any further information/screenshots/recordings etc., please feel free to do so at any time - our engineering team will be happy to review these.

Thanks once again!

<!-- gh-comment-id:3257399375 --> @daniellbw commented on GitHub (Sep 5, 2025): Hi there, Thank you for your report! I was able to reproduce this issue, and I have flagged this to our engineering team. As mentioned by @pamperer562580892423 this might be related to #5777 If you wish to add any further information/screenshots/recordings etc., please feel free to do so at any time - our engineering team will be happy to review these. Thanks once again!
GiteaMirror commented 2026-04-16 22:09:48 -05:00
Author
Owner
Copy Link

@maxkpower commented on GitHub (Sep 5, 2025):

We reproduced the issue on build 2025.8.0. After updating to the latest release 2025.8.1, the issue was no longer present, which suggests it is related to the issue mentioned above #5777

I’ll go ahead and close this issue for now, but please let us know if updating doesn’t resolve it on your side.

<!-- gh-comment-id:3259280515 --> @maxkpower commented on GitHub (Sep 5, 2025): We reproduced the issue on build 2025.8.0. After updating to the latest release 2025.8.1, the issue was no longer present, which suggests it is related to the issue mentioned above [#5777](https://github.com/bitwarden/android/issues/5777) I’ll go ahead and close this issue for now, but please let us know if updating doesn’t resolve it on your side.
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#21600
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?