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

[GH-ISSUE #6857] Login with device generates duplicate notification #50608

New Issue
Open
opened 2026-05-01 13:47:53 -05:00 by GiteaMirror · 7 comments
GiteaMirror commented 2026-05-01 13:47:53 -05:00
Owner
Copy Link

Originally created by @BlackDex on GitHub (Apr 30, 2026).
Original GitHub issue: https://github.com/bitwarden/android/issues/6857

Steps To Reproduce

  1. Have an Android device as a known device for a specific account
  2. Using any browser, login by using Login with device for that same account
  3. See a notification pop to confirm the login
  4. Confirm this login
  5. You are logged in on the web interface
  6. Received a second notification to confirm the login

Expected Result

No duplicate login via device notification on the mobile device, just one.

Actual Result

Received a second notification to approve a login which was already approved, trying to click on approve again results in an error, because that approval is gone already.

Screenshots or Videos

No response

Additional Context

When using Bitwarden Cloud this doesn't happen, only one notification is received.
Looking at the flightrecorder logs it seems that the Cloud version doesn't send a notification to the push servers as there is no log line mentioning BitwardenFirebaseMessagingService – Push Notification Received: AUTH_REQUEST_RESPONSE

On Cloud it can happen also, but only in this situation.

  1. Logout on the mobile device
  2. Login again on the mobile device, but use Login with device now
  3. Approve the request via the web interface
  4. Also see two notifications, one to approve the login, which of course can't be done, but after that also the same notification to approve again.

It looks like the mobile client also shows a notification for the AUTH_REQUEST_RESPONSE, to approve a login, while it probably should just either act upon to finish the login, or ignore it, and not ask the user to approve the login. Maybe a notification that it was successful.

Build Version

2026.4.0 (21434)

What server are you connecting to?

US

Self-host Server Version

Bitwarden Self-Hosted 2026.3.1 AND Bitwarden Cloud 2026.4.0 @ US

Environment Details

Any android device

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 @BlackDex on GitHub (Apr 30, 2026). Original GitHub issue: https://github.com/bitwarden/android/issues/6857 ### Steps To Reproduce 1. Have an Android device as a known device for a specific account 2. Using any browser, login by using `Login with device` for that same account 3. See a notification pop to confirm the login 4. Confirm this login 5. You are logged in on the web interface 6. Received a second notification to confirm the login ### Expected Result No duplicate login via device notification on the mobile device, just one. ### Actual Result Received a second notification to approve a login which was already approved, trying to click on approve again results in an error, because that approval is gone already. ### Screenshots or Videos _No response_ ### Additional Context When using Bitwarden Cloud this doesn't happen, only one notification is received. Looking at the flightrecorder logs it seems that the Cloud version doesn't send a notification to the push servers as there is no log line mentioning `BitwardenFirebaseMessagingService – Push Notification Received: AUTH_REQUEST_RESPONSE` On Cloud it can happen also, but only in this situation. 1. Logout on the mobile device 2. Login again on the mobile device, but use `Login with device` now 3. Approve the request via the web interface 4. Also see two notifications, one to approve the login, which of course can't be done, but after that also the same notification to approve again. It looks like the mobile client also shows a notification for the `AUTH_REQUEST_RESPONSE`, to approve a login, while it probably should just either act upon to finish the login, or ignore it, and not ask the user to approve the login. Maybe a notification that it was successful. ### Build Version 2026.4.0 (21434) ### What server are you connecting to? US ### Self-host Server Version Bitwarden Self-Hosted 2026.3.1 AND Bitwarden Cloud 2026.4.0 @ US ### Environment Details Any android device ### 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-05-01 13:47:53 -05:00
GiteaMirror commented 2026-05-01 13:47:55 -05:00
Author
Owner
Copy Link

@bitwarden-bot commented on GitHub (Apr 30, 2026):

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

<!-- gh-comment-id:4353694193 --> @bitwarden-bot commented on GitHub (Apr 30, 2026): Thank you for your report! We've added this to our internal board for review. ID: [PM-36175](https://bitwarden.atlassian.net/browse/PM-36175) [PM-36175]: https://bitwarden.atlassian.net/browse/PM-36175?atlOrigin=eyJpIjoiNWRkNTljNzYxNjVmNDY3MDlhMDU5Y2ZhYzA5YTRkZjUiLCJwIjoiZ2l0aHViLWNvbS1KU1cifQ
GiteaMirror commented 2026-05-01 13:47:56 -05:00
Author
Owner
Copy Link

@pamperer562580892423 commented on GitHub (Apr 30, 2026):

Regarding your title... "Device Unlock..." should probably be "Login with device..." ?! (PS: just asking for clarity - not meant as nitpicking)

<!-- gh-comment-id:4354604926 --> @pamperer562580892423 commented on GitHub (Apr 30, 2026): Regarding your title... "Device Unlock..." should probably be "Login with device..." ?! (PS: just asking for clarity - not meant as nitpicking)
GiteaMirror commented 2026-05-01 13:47:57 -05:00
Author
Owner
Copy Link

@BlackDex commented on GitHub (Apr 30, 2026):

Regarding your title... "Device Unlock..." should probably be "Login with device..." ?! (PS: just asking for clarity - not meant as nitpicking)

Good one!

<!-- gh-comment-id:4354617779 --> @BlackDex commented on GitHub (Apr 30, 2026): > Regarding your title... "Device Unlock..." should probably be "Login with device..." ?! (PS: just asking for clarity - not meant as nitpicking) Good one!
GiteaMirror commented 2026-05-01 13:47:57 -05:00
Author
Owner
Copy Link

@cbbit commented on GitHub (May 1, 2026):

Hi there,

I am unable to reproduce this issue, it has been escalated for further investigation. If you have more information that can help us, please add it below.

Thanks!

<!-- gh-comment-id:4360181327 --> @cbbit commented on GitHub (May 1, 2026): Hi there, I am unable to reproduce this issue, it has been escalated for further investigation. If you have more information that can help us, please add it below. Thanks!
GiteaMirror commented 2026-05-01 13:47:59 -05:00
Author
Owner
Copy Link

@BlackDex commented on GitHub (May 1, 2026):

You also aren't able to reproduce this on vault.bitwarden.com?
And try to login on the mobile via login with device, and approve via the web interface?

<!-- gh-comment-id:4360193047 --> @BlackDex commented on GitHub (May 1, 2026): You also aren't able to reproduce this on vault.bitwarden.com? And try to login on the mobile via login with device, and approve via the web interface?
GiteaMirror commented 2026-05-01 13:47:59 -05:00
Author
Owner
Copy Link

@pamperer562580892423 commented on GitHub (May 1, 2026):

On Cloud it can happen also, but only in this situation.

  1. Logout on the mobile device
  2. Login again on the mobile device, but use Login with device now
  3. Approve the request via the web interface
  4. Also see two notifications, one to approve the login, which of course can't be done, but after that also the same notification to approve again.

It looks like the mobile client also shows a notification for the AUTH_REQUEST_RESPONSE, to approve a login, while it probably should just either act upon to finish the login, or ignore it, and not ask the user to approve the login. Maybe a notification that it was successful.

I think I could reproduce that on the BW EU cloud.

As I just initiated "Login with device" on the Android app (2026.4.0) and after I approved the login via the browser extension (2026.3.0) on my computer, I also got a notification on the Android app (!) which said "Login requested - Confirm login".

<!-- gh-comment-id:4360410168 --> @pamperer562580892423 commented on GitHub (May 1, 2026): > On Cloud it can happen also, but only in this situation. > > 1. Logout on the mobile device > 2. Login again on the mobile device, but use `Login with device` now > 3. Approve the request via the web interface > 4. Also see two notifications, one to approve the login, which of course can't be done, but after that also the same notification to approve again. > > It looks like the mobile client also shows a notification for the `AUTH_REQUEST_RESPONSE`, to approve a login, while it probably should just either act upon to finish the login, or ignore it, and not ask the user to approve the login. Maybe a notification that it was successful. I think I could reproduce that on the BW EU cloud. As I just initiated "Login with device" on the Android app (2026.4.0) and after I approved the login via the browser extension (2026.3.0) on my computer, I also got a notification on the Android app (!) which said "Login requested - Confirm login".
GiteaMirror commented 2026-05-01 13:48:00 -05:00
Author
Owner
Copy Link

@BlackDex commented on GitHub (May 1, 2026):

@pamperer562580892423 , indeed that is the same i get, but for me at the US servers, and self hosted.

<!-- gh-comment-id:4360828088 --> @BlackDex commented on GitHub (May 1, 2026): @pamperer562580892423 , indeed that is the same i get, but for me at the US servers, and self hosted.
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#50608
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?