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

[GH-ISSUE #2842] Cannot save item to collections when ‘Remove Individual Vault’ is selected and person is set as a user of an org, from iOS share sheet only #49838

New Issue
Closed
opened 2026-05-01 10:27:41 -05:00 by GiteaMirror · 3 comments
GiteaMirror commented 2026-05-01 10:27:41 -05:00
Owner
Copy Link

Originally created by @Gerardv514 on GitHub (Oct 28, 2023).
Original GitHub issue: https://github.com/bitwarden/android/issues/2842

Steps To Reproduce

  1. Go to 'iOS Safari browser, and go to a web page with a login'
  2. Click on 'the iOS share sheet and then select bitwarden so that we can add this webpage login to Bitwarden as a vault item.’
  3. Complete name, user name, password and uri then try and save.

Expected Result

As a user of the organization, there’s no option to choose which collection this item should be saved to, even when the user has permissions to collections.

A user of the org can view all collections when going directly to the Bitwarden iOS app. Collections even show for the user in the desktop browser extension.

Collections just do not show through mobile browser, then share sheet, then click on bitwarden app.

Actual Result

App just spins on saving and does nothing. You need to force close the app. You can never save an item this way.

Screenshots or Videos

No response

Additional Context

No response

Operating System

iOS

Operating System Version

17

Device

iPhone 14 Pro

Build Version

2023.9.2

Beta

  • Using a pre-release version of the application.
Originally created by @Gerardv514 on GitHub (Oct 28, 2023). Original GitHub issue: https://github.com/bitwarden/android/issues/2842 ### Steps To Reproduce 1. Go to 'iOS Safari browser, and go to a web page with a login' 2. Click on 'the iOS share sheet and then select bitwarden so that we can add this webpage login to Bitwarden as a vault item.’ 3. Complete name, user name, password and uri then try and save. ### Expected Result As a user of the organization, there’s no option to choose which collection this item should be saved to, even when the user has permissions to collections. A user of the org can view all collections when going directly to the Bitwarden iOS app. Collections even show for the user in the desktop browser extension. Collections just do not show through mobile browser, then share sheet, then click on bitwarden app. ### Actual Result App just spins on saving and does nothing. You need to force close the app. You can never save an item this way. ### Screenshots or Videos _No response_ ### Additional Context _No response_ ### Operating System iOS ### Operating System Version 17 ### Device iPhone 14 Pro ### Build Version 2023.9.2 ### Beta - [ ] Using a pre-release version of the application.
GiteaMirror added the bug label 2026-05-01 10:27:41 -05:00
GiteaMirror commented 2026-05-01 10:27:45 -05:00
Author
Owner
Copy Link

@Gerardv514 commented on GitHub (Oct 30, 2023):

@djsmith85 Daniel, thanks for your response earlier. Please see this issue that I have created.

Additionally the below issue 1874 issue, which was reported April 2022, maybe the same.

https://github.com/bitwarden/mobile/issues/1874

<!-- gh-comment-id:1785592937 --> @Gerardv514 commented on GitHub (Oct 30, 2023): @djsmith85 Daniel, thanks for your response earlier. Please see this issue that I have created. Additionally the below issue 1874 issue, which was reported April 2022, maybe the same. https://github.com/bitwarden/mobile/issues/1874
GiteaMirror commented 2026-05-01 10:27:47 -05:00
Author
Owner
Copy Link

@SergeantConfused commented on GitHub (Nov 7, 2023):

Hi @Gerardv514,

Thank you for your report. After reviewing the link above, I decided to close this one as it's a duplicate of the report you've mentioned (https://github.com/bitwarden/mobile/issues/1874), in order to consolidate this matter into a single GitHub thread.

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

This issue will now be closed.

Thank you again,

<!-- gh-comment-id:1798481583 --> @SergeantConfused commented on GitHub (Nov 7, 2023): Hi @Gerardv514, Thank you for your report. After reviewing the link above, I decided to close this one as it's a duplicate of the report you've mentioned (https://github.com/bitwarden/mobile/issues/1874), in order to consolidate this matter into a single GitHub thread. If you wish to add any further information/screenshots/recordings etc., please feel free to do so at any time in there - our engineering team will be happy to review these. This issue will now be closed. Thank you again,
GiteaMirror commented 2026-05-01 10:27:52 -05:00
Author
Owner
Copy Link

@Gerardv514 commented on GitHub (Nov 7, 2023):

Hi @Gerardv514,

Thank you for your report. After reviewing the link above, I decided to close this one as it's a duplicate of the report you've mentioned (#1874), in order to consolidate this matter into a single GitHub thread.

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

This issue will now be closed.

Thank you again,

@SergeantConfused Thank you, is it possible to move/merge my initial report from here to #1874, so that the team has a better breakdown on what steps are needed to see this issue?

<!-- gh-comment-id:1798821113 --> @Gerardv514 commented on GitHub (Nov 7, 2023): > Hi @Gerardv514, > > Thank you for your report. After reviewing the link above, I decided to close this one as it's a duplicate of the report you've mentioned (#1874), in order to consolidate this matter into a single GitHub thread. > > If you wish to add any further information/screenshots/recordings etc., please feel free to do so at any time in there - our engineering team will be happy to review these. > > This issue will now be closed. > > Thank you again, @SergeantConfused Thank you, is it possible to move/merge my initial report from here to #1874, so that the team has a better breakdown on what steps are needed to see this issue?
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 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#49838
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?