github-starred/android
2
0
Fork 0
mirror of https://github.com/bitwarden/android.git synced 2026-05-08 04:16:40 -05:00
Code Issues 1.1k Packages Projects Releases 122 Wiki Activity

[GH-ISSUE #4332] Inline Autofill Tab Does Not Display Newly Created Credentials After Save #39037

New Issue
Closed
opened 2026-04-23 17:34:35 -05:00 by GiteaMirror · 5 comments
GiteaMirror commented 2026-04-23 17:34:35 -05:00
Owner
Copy Link

Originally created by @o2rhkzqx on GitHub (Nov 19, 2024).
Original GitHub issue: https://github.com/bitwarden/android/issues/4332

Steps To Reproduce

  1. Navigate to a login or signup page of any app or website.
  2. Open the Bitwarden inline autofill tab on the keyboard.
  3. Select the option to create new credentials.
  4. Fill in the necessary details and click the save button.
  5. Observe the behavior of the inline autofill tab after saving.

Expected Result

After saving the new credentials, the inline autofill tab should update to display all matching credentials, including the newly created ones, rather than switching to the "My Vault" tab.

Actual Result

The inline autofill tab switches to the "My Vault" tab.

Screenshots or Videos

https://github.com/user-attachments/assets/f328f2a6-66d5-415b-bddd-b3ddd0ede90b

Additional Context

When on the login or signup page of any site or app, the Bitwarden inline autofill tab appears on the keyboard if there are matching URLs for already saved credentials. It shows a list to choose from along with an option to create new credentials.
However, after creating new credentials and clicking the save button, the inline autofill tab does not display the newly created credentials alongside the matching ones. Instead, it switches to the "My Vault" tab.

Build Version

Version: 2024.11.5 (19461)

What server are you connecting to?

US

Self-host Server Version

No response

Environment Details

Device: Xiomi K50i
Android Version: Android 14 Xiomi Hyperos

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 @o2rhkzqx on GitHub (Nov 19, 2024). Original GitHub issue: https://github.com/bitwarden/android/issues/4332 ### Steps To Reproduce 1. Navigate to a login or signup page of any app or website. 2. Open the Bitwarden inline autofill tab on the keyboard. 3. Select the option to create new credentials. 4. Fill in the necessary details and click the save button. 5. Observe the behavior of the inline autofill tab after saving. ### Expected Result After saving the new credentials, the inline autofill tab should update to display all matching credentials, including the newly created ones, rather than switching to the "My Vault" tab. ### Actual Result The inline autofill tab switches to the "My Vault" tab. ### Screenshots or Videos https://github.com/user-attachments/assets/f328f2a6-66d5-415b-bddd-b3ddd0ede90b ### Additional Context When on the login or signup page of any site or app, the Bitwarden inline autofill tab appears on the keyboard if there are matching URLs for already saved credentials. It shows a list to choose from along with an option to create new credentials. However, after creating new credentials and clicking the save button, the inline autofill tab does not display the newly created credentials alongside the matching ones. Instead, it switches to the "My Vault" tab. ### Build Version Version: 2024.11.5 (19461) ### What server are you connecting to? US ### Self-host Server Version _No response_ ### Environment Details Device: Xiomi K50i Android Version: Android 14 Xiomi Hyperos ### 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 bugapp:password-manager labels 2026-04-23 17:34:35 -05:00
GiteaMirror commented 2026-04-23 17:34:39 -05:00
Author
Owner
Copy Link

@bitwarden-bot commented on GitHub (Nov 19, 2024):

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

<!-- gh-comment-id:2485062922 --> @bitwarden-bot commented on GitHub (Nov 19, 2024): Thank you for your report! We've added this to our internal board for review. ID: PM-15045
GiteaMirror commented 2026-04-23 17:34:40 -05:00
Author
Owner
Copy Link

@rmcdowell-bitwarden commented on GitHub (Nov 28, 2024):

Hi there,

Thank you for your report!

I was able to reproduce this issue, and I have flagged this 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.

Thanks once again!

<!-- gh-comment-id:2505195988 --> @rmcdowell-bitwarden commented on GitHub (Nov 28, 2024): Hi there, Thank you for your report! I was able to reproduce this issue, and I have flagged this 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. Thanks once again!
GiteaMirror commented 2026-04-23 17:34:42 -05:00
Author
Owner
Copy Link

@closebot-bw commented on GitHub (Aug 12, 2025):

⚠️ Stale Issue Notice

This issue has been automatically marked as stale due to inactivity. It will be closed in 2 weeks (August 26, 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:3177338943 --> @closebot-bw commented on GitHub (Aug 12, 2025): ⚠️ **Stale Issue Notice** This issue has been automatically marked as stale due to inactivity. It will be closed in **2 weeks** (August 26, 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-23 17:34:43 -05:00
Author
Owner
Copy Link

@closebot-bw commented on GitHub (Aug 23, 2025):

🔔 Final Notice - Issue Will Be Closed Soon

This issue was previously marked as stale and will be automatically closed in 3 days (August 26, 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:3216047256 --> @closebot-bw commented on GitHub (Aug 23, 2025): 🔔 **Final Notice - Issue Will Be Closed Soon** This issue was previously marked as stale and will be automatically closed in **3 days** (August 26, 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-23 17:34:44 -05:00
Author
Owner
Copy Link

@closebot-bw commented on GitHub (Aug 26, 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:3222226246 --> @closebot-bw commented on GitHub (Aug 26, 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#39037
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?