github-starred/android
2
0
Fork 0
mirror of https://github.com/bitwarden/android.git synced 2026-06-10 00:28:29 -05:00
Code Issues 2.2k Packages Projects Releases 127 Wiki Activity

[GH-ISSUE #4554] Cipher fields not disabled in view only collection #14758

New Issue
Closed
opened 2026-04-15 00:45:45 -05:00 by GiteaMirror · 5 comments
GiteaMirror commented 2026-04-15 00:45:45 -05:00
Owner
Copy Link

Originally created by @ajasnz on GitHub (Jan 11, 2025).
Original GitHub issue: https://github.com/bitwarden/android/issues/4554

Steps To Reproduce

  1. Create a collection
  2. Add a cipher to the collection
  3. Assign a member view only permissions to the collection
  4. Using the member with view only access open the cipher in edit mode
  5. Try to edit a field
  6. Click save

Expected Result

Cipher fields have a disabled state and the user cannot alter the field. A useful error message is displayed when clicking save to explain the item is view only

Actual Result

The user is able to change field contents (not saved) giving the impression they can edit the cipher and potentially leading to lost login details.
When clicking save the error message is "you must assign at least one collection" which is not an accurate representation of the issue

Screenshots or Videos

No response

Additional Context

No response

Build Version

2025.1

What server are you connecting to?

US

Self-host Server Version

No response

Environment Details

Device: Samsung galaxy s23+
OS: Android 15, one UI 6

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 @ajasnz on GitHub (Jan 11, 2025). Original GitHub issue: https://github.com/bitwarden/android/issues/4554 ### Steps To Reproduce 1. Create a collection 2. Add a cipher to the collection 3. Assign a member view only permissions to the collection 4. Using the member with view only access open the cipher in edit mode 5. Try to edit a field 6. Click save ### Expected Result Cipher fields have a disabled state and the user cannot alter the field. A useful error message is displayed when clicking save to explain the item is view only ### Actual Result The user is able to change field contents (not saved) giving the impression they can edit the cipher and potentially leading to lost login details. When clicking save the error message is "you must assign at least one collection" which is not an accurate representation of the issue ### Screenshots or Videos _No response_ ### Additional Context _No response_ ### Build Version 2025.1 ### What server are you connecting to? US ### Self-host Server Version _No response_ ### Environment Details Device: Samsung galaxy s23+ OS: Android 15, one UI 6 ### 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 2026-04-15 00:45:45 -05:00
GiteaMirror commented 2026-04-15 00:45:48 -05:00
Author
Owner
Copy Link

@bitwarden-bot commented on GitHub (Jan 11, 2025):

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

<!-- gh-comment-id:2585195285 --> @bitwarden-bot commented on GitHub (Jan 11, 2025): Thank you for your report! We've added this to our internal board for review. ID: PM-16963
GiteaMirror commented 2026-04-15 00:45:49 -05:00
Author
Owner
Copy Link

@SergeantConfused commented on GitHub (Jan 11, 2025):

Hello @ajasnz,

Thank you for your report. I was able to reproduce this behaviour and have flagged it to the Engineering department.
Please feel free to post additional information, such as screenshots or a screen video recordings, if you wish.

Thank you again,

<!-- gh-comment-id:2585291296 --> @SergeantConfused commented on GitHub (Jan 11, 2025): Hello @ajasnz, Thank you for your report. I was able to reproduce this behaviour and have flagged it to the Engineering department. Please feel free to post additional information, such as screenshots or a screen video recordings, if you wish. Thank you again,
GiteaMirror commented 2026-04-15 00:45:50 -05:00
Author
Owner
Copy Link

@closebot-bw commented on GitHub (Nov 18, 2025):

⚠️ Stale Issue Notice

This issue has been automatically marked as stale due to inactivity. It will be closed in 2 weeks (December 02, 2025) if no further activity occurs.

If this issue is still relevant and you would like to keep it open, please:

  • Comment on this issue to show continued interest
  • Provide any additional information or updates
  • Confirm that the issue still exists in the latest version

Thank you for your contribution to this project! 🙏

<!-- gh-comment-id:3548198993 --> @closebot-bw commented on GitHub (Nov 18, 2025): ⚠️ **Stale Issue Notice** This issue has been automatically marked as stale due to inactivity. It will be closed in **2 weeks** (December 02, 2025) if no further activity occurs. If this issue is still relevant and you would like to keep it open, please: - Comment on this issue to show continued interest - Provide any additional information or updates - Confirm that the issue still exists in the latest version Thank you for your contribution to this project! 🙏
GiteaMirror commented 2026-04-15 00:45:51 -05:00
Author
Owner
Copy Link

@closebot-bw commented on GitHub (Nov 29, 2025):

🔔 Final Notice - Issue Will Be Closed Soon

This issue was previously marked as stale and will be automatically closed in 3 days (December 02, 2025) if no further activity occurs.

If you're still experiencing this issue or believe it should remain open, please comment below to prevent automatic closure.

We appreciate your understanding and contribution to keeping our issue tracker organized! 📋

<!-- gh-comment-id:3591823440 --> @closebot-bw commented on GitHub (Nov 29, 2025): 🔔 **Final Notice - Issue Will Be Closed Soon** This issue was previously marked as stale and will be automatically closed in **3 days** (December 02, 2025) if no further activity occurs. If you're still experiencing this issue or believe it should remain open, please comment below to prevent automatic closure. We appreciate your understanding and contribution to keeping our issue tracker organized! 📋
GiteaMirror commented 2026-04-15 00:45:52 -05:00
Author
Owner
Copy Link

@closebot-bw commented on GitHub (Dec 4, 2025):

🔒 Issue Closed Due to Inactivity

This issue has been automatically closed due to lack of activity for an extended period. We periodically review and close inactive issues to help maintain our issue tracker and focus on current priorities.

If this issue is still relevant:

  • Please create a new issue with updated information
  • Include steps to reproduce the problem if it's a bug report
  • Mention if this issue still occurs in the latest version

Thank you for your contribution to this project. Your feedback helps us improve! 🙏

<!-- gh-comment-id:3612605071 --> @closebot-bw commented on GitHub (Dec 4, 2025): 🔒 **Issue Closed Due to Inactivity** This issue has been automatically closed due to lack of activity for an extended period. We periodically review and close inactive issues to help maintain our issue tracker and focus on current priorities. **If this issue is still relevant:** - Please create a new issue with updated information - Include steps to reproduce the problem if it's a bug report - Mention if this issue still occurs in the latest version Thank you for your contribution to this project. Your feedback helps us improve! 🙏
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#14758
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?