Collection is not visible if two accounts are logged in

calebdias commented 2 months ago

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

Steps To Reproduce

Log in with a BW account (account "A") that has access to an Organization's Collection.
From the same app, log in to a different BW account (account "B") that has access to the same Collection.
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.

bitwarden-bot commented 2 months ago

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

sammbw commented 2 months ago

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!

starktower007 commented 2 months ago

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.

calebdias commented 2 months ago

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!

Thank you for looking into this. Let me know if there are any specific questions I can answer, or ways I can help with further testing.

justrightlizard commented 1 month ago

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:

Using version 2024.9.1 (19099)
Account A is a premium user.
Account B is a free user.
Using the free tier of organizations.
Two collections created in total.
Account A has the Owner role
Account B has the User role.
Account A has the "can manage" permission for both collections.
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.

bitwarden / android