github-starred/android
2
0
Fork 0
mirror of https://github.com/bitwarden/android.git synced 2026-03-22 20:41:29 -05:00
Code Issues 144 Packages Projects Releases 118 Wiki Activity

Unsaved field lost when hitting back button without notice #2118

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

Originally created by @oldium on GitHub (Jan 5, 2025).

Steps To Reproduce

  1. Go to Secured notes
  2. Select an existing note
  3. Click to start editing
  4. Add new field
  5. Fill-in some data
  6. Press Android back button

Expected Result

A dialog that there are unsaved data is shown

Actual Result

The changes are lost without notice

Screenshots or Videos

No response

Additional Context

No response

Build Version

2024.10.0 (11270)

What server are you connecting to?

Self-host

Self-host Server Version

2024.12.1

Environment Details

  • Samsung Galaxy S21 FE

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 @oldium on GitHub (Jan 5, 2025). ### Steps To Reproduce 1. Go to Secured notes 2. Select an existing note 3. Click to start editing 4. Add new field 5. Fill-in some data 6. Press Android back button ### Expected Result A dialog that there are unsaved data is shown ### Actual Result The changes are lost without notice ### Screenshots or Videos _No response_ ### Additional Context _No response_ ### Build Version 2024.10.0 (11270) ### What server are you connecting to? Self-host ### Self-host Server Version 2024.12.1 ### Environment Details - Samsung Galaxy S21 FE ### 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 bug label 2025-11-26 23:08:34 -06:00
GiteaMirror commented 2025-11-26 23:08:34 -06:00
Author
Owner
Copy Link

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

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

@bitwarden-bot commented on GitHub (Jan 5, 2025): Thank you for your report! We've added this to our internal board for review. ID: PM-16724
GiteaMirror commented 2025-11-26 23:08:35 -06:00
Author
Owner
Copy Link

@Greenderella commented on GitHub (Jan 6, 2025):

Hi there,

Your issue appears to be describing the intended behavior of the software at the moment. If you want this to be changed, it would be a feature request.

We use GitHub issues as a place to track bugs and other development related issues. The Bitwarden Community Forums has a Feature Requests section for submitting, voting for, and discussing requests like this one: https://community.bitwarden.com/c/feature-requests/

Please sign up on our forums (https://community.bitwarden.com/signup) and search to see if this request already exists. If so, you can vote for it and contribute to any discussions about it. If not, you can re-create the request there so that it can be properly tracked.

This issue will now be closed.

Thanks!

@Greenderella commented on GitHub (Jan 6, 2025): Hi there, Your issue appears to be describing the intended behavior of the software at the moment. If you want this to be changed, it would be a feature request. We use GitHub issues as a place to track bugs and other development related issues. The Bitwarden Community Forums has a Feature Requests section for submitting, voting for, and discussing requests like this one: https://community.bitwarden.com/c/feature-requests/ Please sign up on our forums (https://community.bitwarden.com/signup) and search to see if this request already exists. If so, you can vote for it and contribute to any discussions about it. If not, you can re-create the request there so that it can be properly tracked. This issue will now be closed. Thanks!
GiteaMirror commented 2025-11-26 23:08:35 -06:00
Author
Owner
Copy Link

@oldium commented on GitHub (Jan 6, 2025):

So why Web UI asks for confirmation when Android UI does not? Both UIs behave differently, so this is definitely not expected. I lost 4 hours yesterday fixing the issue after lost password due to this bug.

@oldium commented on GitHub (Jan 6, 2025): So why Web UI asks for confirmation when Android UI does not? Both UIs behave differently, so this is definitely not expected. I lost 4 hours yesterday fixing the issue after lost password due to this bug.
GiteaMirror commented 2025-11-26 23:08:35 -06:00
Author
Owner
Copy Link

@oldium commented on GitHub (Jan 6, 2025):

Screenshot from Web UI with the confirmation dialog.
image

Lost changes should never be “intended behaviour”, sorry.

@oldium commented on GitHub (Jan 6, 2025): Screenshot from Web UI with the confirmation dialog. ![image](https://github.com/user-attachments/assets/9f039eee-fb37-4192-abdf-ee6818aacc7d) Lost changes should _never_ be “intended behaviour”, sorry.
GiteaMirror commented 2025-11-26 23:08:35 -06:00
Author
Owner
Copy Link

@oldium commented on GitHub (Jan 6, 2025):

The feature request exists already: https://community.bitwarden.com/t/warning-prompt-when-closing-apps-with-unsaved-information/51744

It is incredibly sad that such feature request must exist...

@oldium commented on GitHub (Jan 6, 2025): The feature request exists already: https://community.bitwarden.com/t/warning-prompt-when-closing-apps-with-unsaved-information/51744 It is incredibly sad that such feature request must exist...
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#2118
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?