github-starred/android
2
0
Fork 0
mirror of https://github.com/bitwarden/android.git synced 2026-03-09 03:33:36 -05:00
Code Issues 144 Packages Projects Releases 116 Wiki Activity

Collection is not visible if two accounts are logged in #1974

New Issue
Open
opened 2025-11-26 23:03:31 -06:00 by GiteaMirror · 8 comments
GiteaMirror commented 2025-11-26 23:03:31 -06:00
Owner
Copy Link

Originally created by @calebdias on GitHub (Aug 18, 2024).

Bitwarden Beta

  • I'm using the new native Bitwarden Beta app and I'm aware that legacy .NET app bugs should be reported in bitwarden/mobile

Steps To Reproduce

  1. Log in with a BW account (account "A") that has access to an Organization's Collection.
  2. From the same app, log in to a different BW account (account "B") that has access to the same Collection.
  3. Now switch back to account "A". The collection is no longer visible.

Expected Result

Ability to sign in with two BW accounts and access a shared Collection from each. (This works as expected in the legacy app).

Actual Result

When I log in with two BW accounts that have access to the same Collection, only the second BW account can see the Collection.

Screenshots or Videos

No response

Additional Context

Upon initial login, account "A" has access to the shared Collection as expected. Only once account"B" logs in, does account "A" lose access to the Collection.

Build Version

2024.7.3 (18938)

Environment Details

Google Pixel 7a, GrapheneOS.

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 @calebdias on GitHub (Aug 18, 2024). ### Bitwarden Beta - [x] I'm using the new native Bitwarden Beta app and I'm aware that legacy .NET app bugs should be reported in [bitwarden/mobile](https://github.com/bitwarden/mobile) ### Steps To Reproduce 1. Log in with a BW account (account "A") that has access to an Organization's Collection. 2. From the same app, log in to a different BW account (account "B") that has access to the same Collection. 3. Now switch back to account "A". The collection is no longer visible. ### Expected Result Ability to sign in with two BW accounts and access a shared Collection from each. (This works as expected in the legacy app). ### Actual Result When I log in with two BW accounts that have access to the same Collection, only the second BW account can see the Collection. ### Screenshots or Videos _No response_ ### Additional Context Upon initial login, account "A" has access to the shared Collection as expected. Only once account"B" logs in, does account "A" lose access to the Collection. ### Build Version 2024.7.3 (18938) ### Environment Details Google Pixel 7a, GrapheneOS. ### 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 2025-11-26 23:03:31 -06:00
GiteaMirror commented 2025-11-26 23:03:32 -06:00
Author
Owner
Copy Link

@bitwarden-bot commented on GitHub (Aug 18, 2024):

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

@bitwarden-bot commented on GitHub (Aug 18, 2024): Thank you for your report! We've added this to our internal board for review. ID: PM-11034
GiteaMirror commented 2025-11-26 23:03:32 -06:00
Author
Owner
Copy Link

@sammbw commented on GitHub (Aug 19, 2024):

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!

@sammbw commented on GitHub (Aug 19, 2024): 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 2025-11-26 23:03:32 -06:00
Author
Owner
Copy Link

@shell-surfer commented on GitHub (Aug 20, 2024):

I could reproduce this issue and it does indeed behave as @calebdias pointed out.

I also noticed that even logging out account "B" doesn't show the collection back in account "A".

The only ways to show the collection again in account A are

  • Log out account A and log in back again. This shows the collection back in account A in the app. This also stops the collection from showing up in account B in the process.
  • Edit and save a login or any other action that forces a sync from account A. This shows the collection back in account A in the app. This also stops the collection from showing up in account B in the process.

If you log out and log in from account "B" again, the collection again shows up only in account B.

@shell-surfer commented on GitHub (Aug 20, 2024): I could reproduce this issue and it does indeed behave as @calebdias pointed out. I also noticed that even logging out account "B" doesn't show the collection back in account "A". The only ways to show the collection again in account A are - Log out account A and log in back again. This shows the collection back in account A in the app. This also stops the collection from showing up in account B in the process. - Edit and save a login or any other action that forces a sync from account A. This shows the collection back in account A in the app. This also stops the collection from showing up in account B in the process. If you log out and log in from account "B" again, the collection again shows up only in account B.
GiteaMirror commented 2025-11-26 23:03:32 -06:00
Author
Owner
Copy Link

@justrightlizard commented on GitHub (Sep 9, 2024):

I can reproduce the issue using the exact same steps from @calebdias's initial post and @starktower007's comment.

Here are a few notes about my situation:

  1. Using version 2024.9.1 (19099)
  2. Account A is a premium user.
  3. Account B is a free user.
  4. Using the free tier of organizations.
  5. Two collections created in total.
  6. Account A has the Owner role
  7. Account B has the User role.
  8. Account A has the "can manage" permission for both collections.
  9. Account B has the "can edit" permission for both collections

I'm not sure how much of that matters, but I figured I'd add as much detail about the situation as possible.

@justrightlizard commented on GitHub (Sep 9, 2024): I can reproduce the issue using the exact same steps from @calebdias's initial post and @starktower007's comment. Here are a few notes about my situation: 1. Using version 2024.9.1 (19099) 2. Account A is a premium user. 3. Account B is a free user. 4. Using the free tier of organizations. 5. Two collections created in total. 6. Account A has the Owner role 7. Account B has the User role. 8. Account A has the "can manage" permission for both collections. 9. Account B has the "can edit" permission for both collections I'm not sure how much of that matters, but I figured I'd add as much detail about the situation as possible.
GiteaMirror commented 2025-11-26 23:03:32 -06:00
Author
Owner
Copy Link

@calebdias commented on GitHub (Dec 21, 2024):

Any plans to fix this? This bug still affects the latest stable version.

@calebdias commented on GitHub (Dec 21, 2024): Any plans to fix this? This bug still affects the latest stable version.
GiteaMirror commented 2025-11-26 23:03:33 -06:00
Author
Owner
Copy Link

@justrightlizard commented on GitHub (Dec 21, 2024):

Any plans to fix this? This bug still affects the latest stable version.

Yep, it still affects the latest pre-release as well. 2024.12.0 (19597)

Would love to see this fixed. Currently, I have to have both the pre-release and pre-release beta version installed on my phone to fulfill my use case.

@justrightlizard commented on GitHub (Dec 21, 2024): > Any plans to fix this? This bug still affects the latest stable version. Yep, it still affects the latest pre-release as well. 2024.12.0 (19597) Would love to see this fixed. Currently, I have to have both the pre-release and pre-release beta version installed on my phone to fulfill my use case.
GiteaMirror commented 2025-11-26 23:03:33 -06:00
Author
Owner
Copy Link

@calebdias commented on GitHub (Jan 8, 2025):

I found a workaround... Clicking the menu, then "sync" (not dragging down to refresh) will make the collection reappear.

You will have to do this again if you want the collection to be visible from another account.

@calebdias commented on GitHub (Jan 8, 2025): I found a workaround... Clicking the menu, then "sync" (not dragging down to refresh) will make the collection reappear. You will have to do this again if you want the collection to be visible from another account.
GiteaMirror commented 2025-11-26 23:03:33 -06:00
Author
Owner
Copy Link

@pquantin commented on GitHub (Apr 14, 2025):

The issue (and proposed workaround) is still present in 2025.3.0 version.

@pquantin commented on GitHub (Apr 14, 2025): The issue (and proposed workaround) is still present in 2025.3.0 version.
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#1974
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?