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

Cannot save new login if personal ownership is disabled #1439

New Issue
Closed
opened 2025-11-26 22:49:08 -06:00 by GiteaMirror · 11 comments
GiteaMirror commented 2025-11-26 22:49:08 -06:00
Owner
Copy Link

Originally created by @oglodyte on GitHub (Apr 5, 2022).

Steps To Reproduce

  1. disable personal ownership in the organization policy
  2. go to any site (cnn.com) in mobile Safari and try to create new login using Bitwarden extension

Expected Result

Login saved

Actual Result

Extension hands on saving new login
New login is not saved

Screenshots or Videos

No response

Additional Context

Extension does not offer to set the collection for the new login and it is mandatory when personal ownership is disabled.

Proposed Solution(s):

  1. Add the ability to select collections for the new item
  2. Add the ability to define default collection for the new items (per organization, for the person or both). This collection should be applied to new items by default if not specified otherwise.

Operating System

iOS

Operating System Version

15.4.1

Device

iPhone 13 Pro Max

Build Version

12.17.0 (1626)

Beta

  • Using a pre-release version of the application.
Originally created by @oglodyte on GitHub (Apr 5, 2022). ### Steps To Reproduce 1. disable personal ownership in the organization policy 2. go to any site (cnn.com) in mobile Safari and try to create new login using Bitwarden extension ### Expected Result Login saved ### Actual Result Extension hands on saving new login New login is not saved ### Screenshots or Videos _No response_ ### Additional Context Extension does not offer to set the collection for the new login and it is mandatory when personal ownership is disabled. Proposed Solution(s): 1. Add the ability to select collections for the new item 2. Add the ability to define default collection for the new items (per organization, for the person or both). This collection should be applied to new items by default if not specified otherwise. ### Operating System iOS ### Operating System Version 15.4.1 ### Device iPhone 13 Pro Max ### Build Version 12.17.0 (1626) ### Beta - [ ] Using a pre-release version of the application.
GiteaMirror added the bug label 2025-11-26 22:49:08 -06:00
GiteaMirror commented 2025-11-26 22:49:09 -06:00
Author
Owner
Copy Link

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

Just found this here. An issue was discovered when Single Organization & Remove Individual Vault options were turned on for an organization. We reported an issue with the browser extension here: https://github.com/bitwarden/clients/pull/4808.

I have also determined that same user when using iOS Safari browser attempting to save a new item, when they use the share sheet they do not have any access to any collections. When they save the item they just get a spinning circle and "saving." I believe the problem is due to them not having the ability to choose which collection to save the item to. If they exit out and go into the Bitwarden iOS app, they are able to save the item there since they are able to choose which collection to save the item to.

@oglodyte has created this more than a year and half ago and still hasn't been fix.

@Gerardv514 commented on GitHub (Oct 24, 2023): Just found this here. An issue was discovered when Single Organization & Remove Individual Vault options were turned on for an organization. We reported an issue with the browser extension here: [https://github.com/bitwarden/clients/pull/4808](url). I have also determined that same user when using iOS Safari browser attempting to save a new item, when they use the share sheet they do not have any access to any collections. When they save the item they just get a spinning circle and "saving." I believe the problem is due to them not having the ability to choose which collection to save the item to. If they exit out and go into the Bitwarden iOS app, they are able to save the item there since they are able to choose which collection to save the item to. @oglodyte has created this more than a year and half ago and still hasn't been fix.
GiteaMirror commented 2025-11-26 22:49:09 -06:00
Author
Owner
Copy Link

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

Does anyone need more of a step by step breakdown to replicate this? Is there not enough information provided to reproduce?

I’m looking to do whatever I can to have this resolved. If this can’t be reproduced please advise and maybe a better explanation can be provided.

@Gerardv514 commented on GitHub (Oct 25, 2023): Does anyone need more of a step by step breakdown to replicate this? Is there not enough information provided to reproduce? I’m looking to do whatever I can to have this resolved. If this can’t be reproduced please advise and maybe a better explanation can be provided.
GiteaMirror commented 2025-11-26 22:49:09 -06:00
Author
Owner
Copy Link

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

@dwbit @trmartin4 @kspearrin

if you can reproduce this, can you at least put this on the teams radar. I have a feeling this hasn’t been looked at..at all but I can surely reproduce. Additionally there was some work similar to this setup, done on the browser extension side.

@Gerardv514 commented on GitHub (Oct 25, 2023): @dwbit @trmartin4 @kspearrin if you can reproduce this, can you at least put this on the teams radar. I have a feeling this hasn’t been looked at..at all but I can surely reproduce. Additionally there was some work similar to this setup, done on the browser extension side.
GiteaMirror commented 2025-11-26 22:49:10 -06:00
Author
Owner
Copy Link

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

Hi everyone,

Thank you for your reports. I was able to reproduce this behaviour and I have flagged it to our Engineering team.

If you wish to add any further information, such as screenshots or screen recordings, please feel free to do so at any time - our Engineering team will be happy to review them.

Thank you again,

@SergeantConfused commented on GitHub (Nov 7, 2023): Hi everyone, Thank you for your reports. I was able to reproduce this behaviour and I have flagged it to our Engineering team. If you wish to add any further information, such as screenshots or screen recordings, please feel free to do so at any time - our Engineering team will be happy to review them. Thank you again,
GiteaMirror commented 2025-11-26 22:49:10 -06:00
Author
Owner
Copy Link

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

Hi everyone,

Thank you for your reports. I was able to reproduce this behaviour and I have flagged it to our Engineering team.

If you wish to add any further information, such as screenshots or screen recordings, please feel free to do so at any time - our Engineering team will be happy to review them.

Thank you again,

@SergeantConfused is this on their list to fix? Any expectation of when this would start being worked on , this year ? 2024? 2025?

Thank you

@Gerardv514 commented on GitHub (Nov 18, 2023): > Hi everyone, > > Thank you for your reports. I was able to reproduce this behaviour and I have flagged it to our Engineering team. > > If you wish to add any further information, such as screenshots or screen recordings, please feel free to do so at any time - our Engineering team will be happy to review them. > > Thank you again, @SergeantConfused is this on their list to fix? Any expectation of when this would start being worked on , this year ? 2024? 2025? Thank you
GiteaMirror commented 2025-11-26 22:49:10 -06:00
Author
Owner
Copy Link

@Gerardv514 commented on GitHub (Jan 23, 2024):

Any update on this???

@Gerardv514 commented on GitHub (Jan 23, 2024): Any update on this???
GiteaMirror commented 2025-11-26 22:49:10 -06:00
Author
Owner
Copy Link

@Gerardv514 commented on GitHub (Feb 3, 2024):

@SergeantConfused is this moving along????

@Gerardv514 commented on GitHub (Feb 3, 2024): @SergeantConfused is this moving along????
GiteaMirror commented 2025-11-26 22:49:10 -06:00
Author
Owner
Copy Link

@Gerardv514 commented on GitHub (Feb 16, 2024):

@bitwarden-devops-bot any update?

@Gerardv514 commented on GitHub (Feb 16, 2024): @bitwarden-devops-bot any update?
GiteaMirror commented 2025-11-26 22:49:11 -06:00
Author
Owner
Copy Link

@Gerardv514 commented on GitHub (Feb 19, 2024):

@djsmith85 any update on this?

@Gerardv514 commented on GitHub (Feb 19, 2024): @djsmith85 any update on this?
GiteaMirror commented 2025-11-26 22:49:11 -06:00
Author
Owner
Copy Link

@Gerardv514 commented on GitHub (Apr 6, 2024):

I just lost 2 organizational clients due to this.

@Gerardv514 commented on GitHub (Apr 6, 2024): I just lost 2 organizational clients due to this.
GiteaMirror commented 2025-11-26 22:49:11 -06:00
Author
Owner
Copy Link

@vvolkgang commented on GitHub (Jun 20, 2024):

Issue migrated to https://github.com/bitwarden/mobile/issues/1874

@vvolkgang commented on GitHub (Jun 20, 2024): Issue migrated to https://github.com/bitwarden/mobile/issues/1874
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#1439
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?