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

New items being saved to incorrect folder when using Safari autofill #1263

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

Originally created by @hampton8 on GitHub (Apr 3, 2021).

When I create a new login entry using the autofill prompt within Safari on iOS and select a folder, the new login item is actually saved to the folder the comes after the one selected. For example: let's say I have three folders - A, B and C - and I create a new login entry in my BitWarden vault using the Safari autofill interface, and I choose to save the new entry to folder B. When I open the BitWarden app, I will find that the new entry has in fact been saved to folder C, not B. See my comment below for a more accurate description.

Originally created by @hampton8 on GitHub (Apr 3, 2021). When I create a new login entry using the autofill prompt within Safari on iOS and select a folder, the new login item is actually saved to the folder the comes after the one selected. ~~For example: let's say I have three folders - A, B and C - and I create a new login entry in my BitWarden vault using the Safari autofill interface, and I choose to save the new entry to folder B. When I open the BitWarden app, I will find that the new entry has in fact been saved to folder C, not B.~~ **See my comment below for a more accurate description.**
GiteaMirror commented 2025-11-26 22:43:13 -06:00
Author
Owner
Copy Link

@SergeantConfused commented on GitHub (Apr 3, 2021):

Hi there,

I opened Safari, went to https://vault.bitwarden.com/#/, tapped on the email address field, tapped on the Key above the keyboard, tapped on Bitwarden, then created a new item and assigned it to Folder 'B' and it was saved into folder 'B', not 'C'. I've tested this on an iPhone SE 2020 running iOS 14.4.1. Please uninstall Bitwarden off your iOS device, turn your device off and back on, reinstall Bitwarden from the Apple App Store, and let me know if this behaviour persists.

I thank you in advance for your understanding and cooperation.

All the best,

@SergeantConfused commented on GitHub (Apr 3, 2021): Hi there, I opened Safari, went to https://vault.bitwarden.com/#/, tapped on the email address field, tapped on the Key above the keyboard, tapped on Bitwarden, then created a new item and assigned it to Folder 'B' and it was saved into folder 'B', not 'C'. I've tested this on an iPhone SE 2020 running iOS 14.4.1. Please uninstall Bitwarden off your iOS device, turn your device off and back on, reinstall Bitwarden from the Apple App Store, and let me know if this behaviour persists. I thank you in advance for your understanding and cooperation. All the best,
GiteaMirror commented 2025-11-26 22:43:14 -06:00
Author
Owner
Copy Link

@hampton8 commented on GitHub (Apr 3, 2021):

Hi @SergeantConfused

I've uninstalled Bitwarden, turned my phone off and on again, and reinstalled it, and I can confirm that the issue is still present - although it seems my generalisation in the original post was wrong, since strangely when I create a folder called 'B' and save a login to it via Safari, it does actually save there. However, for certain other folders it does not. Items saved to 'Productivity' are actually saved to 'Safes, Padlocks, Gates & Doors', 'School & College' are actually saved to the first subfolder ('School & College/School Name'), 'Shopping' becomes 'Social', 'Social' becomes 'Software Licences', 'Software Licences' becomes 'Technology' and 'Technology' becomes 'Travel'.

Other folders, however, work fine, including 'Banking', 'Health & Fitness' and 'Money'.

This issue is also present on my iPad Air 2, as well as my iPhone 11, and I'm a Bitwarden Premium subscriber. This bug is present when adding a new login item by tapping the key on the autofill pop up (as you did) or by tapping on 'Bitwarden' from the share menu in Safari. This bug is not present when adding a new login entry from within the Bitwarden app.

@hampton8 commented on GitHub (Apr 3, 2021): Hi @SergeantConfused I've uninstalled Bitwarden, turned my phone off and on again, and reinstalled it, and I can confirm that the issue is still present - although it seems my generalisation in the original post was wrong, since strangely when I create a folder called 'B' and save a login to it via Safari, it _does_ actually save there. However, for certain other folders it does not. Items saved to 'Productivity' are actually saved to 'Safes, Padlocks, Gates & Doors', 'School & College' are actually saved to the first subfolder ('School & College/School Name'), 'Shopping' becomes 'Social', 'Social' becomes 'Software Licences', 'Software Licences' becomes 'Technology' and 'Technology' becomes 'Travel'. Other folders, however, work fine, including 'Banking', 'Health & Fitness' and 'Money'. This issue is also present on my iPad Air 2, as well as my iPhone 11, and I'm a Bitwarden Premium subscriber. This bug is present when adding a new login item by tapping the key on the autofill pop up (as you did) or by tapping on 'Bitwarden' from the share menu in Safari. This bug is not present when adding a new login entry from within the Bitwarden app.
GiteaMirror commented 2025-11-26 22:43:14 -06:00
Author
Owner
Copy Link

@lychengrex commented on GitHub (May 13, 2022):

I have the same issue. It seems that the folder is always going to be the next in the sequence. 🤔

@lychengrex commented on GitHub (May 13, 2022): I have the same issue. It seems that the folder is always going to be the next in the sequence. 🤔
GiteaMirror commented 2025-11-26 22:43:14 -06:00
Author
Owner
Copy Link

@SergeantConfused commented on GitHub (Oct 2, 2023):

Hello everyone,

Thank you, @hampton8, for your detailed response. I was able to reproduce this behaviour on iOS 17.0.2 with Bitwarden 2023.9.1, and have flagged this internally to our engineering team.

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

Thank you again,

@SergeantConfused commented on GitHub (Oct 2, 2023): Hello everyone, Thank you, @hampton8, for your detailed response. I was able to reproduce this behaviour on iOS 17.0.2 with Bitwarden 2023.9.1, and have flagged this internally to our engineering team. If you wish to add any further information/screenshots/recordings etc., please feel free to do so at any time - our engineering team will be happy to review these. Thank you again,
GiteaMirror commented 2025-11-26 22:43:15 -06:00
Author
Owner
Copy Link

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

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

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