Autofill issues since ver. 2024.8.0 (18985) #1976

Closed
opened 2025-11-26 23:03:34 -06:00 by GiteaMirror · 3 comments
Owner

Originally created by @derei on GitHub (Aug 19, 2024).

Bitwarden Beta

  • I'm using the new native Bitwarden Beta app and I'm aware that legacy .NET app bugs should be reported in bitwarden/mobile

Steps To Reproduce

Since the latest Bitwarden update, the autofill works unpredictably, from not working at all, to randomly or partly working (eg. fills the username but fails to fill the password).

The erratic behaviour is not linked to a specific app or browser. Sometimes, in the same browser (I'm using Vanadium and Kiwi), it works, and some other times it doesn't. For apps, is equally random.

Also, I noticed on some occasions that autofill settings were disabled in Bitwarden (I didn't disable them), but reenabling the settings didn't restore reliable autofill functionality.

Expected Result

I would expect the autofill to work predictably and reliably, as it used to work before.

Actual Result

It's been explained in the introduction.

Screenshots or Videos

No response

Additional Context

No response

Build Version

Version: 2024.8.0 (18985)

Environment Details

  • Google Pixel 7 Pro

  • GrapheneOS 2024080600 (Android 14)

  • Vanadium Browser 127.0.6533.104.1

  • Kiwi Browser 124.0.6327.4

  • Insular 6.4 - 66CD8034

  • using Bitwarden in both main profile and work profile managed by Insular.

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 @derei on GitHub (Aug 19, 2024). ### Bitwarden Beta - [X] I'm using the new native Bitwarden Beta app and I'm aware that legacy .NET app bugs should be reported in [bitwarden/mobile](https://github.com/bitwarden/mobile) ### Steps To Reproduce Since the latest Bitwarden update, the autofill works unpredictably, from not working at all, to randomly or partly working (eg. fills the username but fails to fill the password). The erratic behaviour is not linked to a specific app or browser. Sometimes, in the same browser (I'm using Vanadium and Kiwi), it works, and some other times it doesn't. For apps, is equally random. Also, I noticed on some occasions that autofill settings were disabled in Bitwarden (I didn't disable them), but reenabling the settings didn't restore reliable autofill functionality. ### Expected Result I would expect the autofill to work predictably and reliably, as it used to work before. ### Actual Result It's been explained in the introduction. ### Screenshots or Videos _No response_ ### Additional Context _No response_ ### Build Version Version: 2024.8.0 (18985) ### Environment Details - Google Pixel 7 Pro - GrapheneOS 2024080600 (Android 14) - Vanadium Browser 127.0.6533.104.1 - Kiwi Browser 124.0.6327.4 - Insular 6.4 - 66CD8034 - using Bitwarden in both main profile and work profile managed by Insular. ### 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:03:34 -06:00
Author
Owner

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

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

@bitwarden-bot commented on GitHub (Aug 19, 2024): Thank you for your report! We've added this to our internal board for review. ID: PM-11113
Author
Owner

@Greenderella commented on GitHub (Aug 19, 2024):

Hi there!

We appreciate you letting us know of this issue. Due to the nature of autofill issues, we track them internally using different Forms depending on the platform:

mobile: https://docs.google.com/forms/d/e/1FAIpQLScMopHyN7KGJs8hW562VTzbIGL4KcFnx0wJcsW0GYE1BnPiGA/viewform

browser extension: https://docs.google.com/forms/d/e/1FAIpQLSfkxh1w6vK8fLYwAbAAEVhvhMAJwfFNDtYtPUVk1y5WTHvJmQ/viewform

In this case, we will go ahead and file an autofill report for you with the information you added here.

In the future, if you encounter any other page or app that doesn't autofill as expected, please avoid opening a new GitHub issue and go directly to the corresponding form.

This issue will now be closed.

Thanks!

@Greenderella commented on GitHub (Aug 19, 2024): Hi there! We appreciate you letting us know of this issue. Due to the nature of autofill issues, we track them internally using different Forms depending on the platform: mobile: https://docs.google.com/forms/d/e/1FAIpQLScMopHyN7KGJs8hW562VTzbIGL4KcFnx0wJcsW0GYE1BnPiGA/viewform browser extension: https://docs.google.com/forms/d/e/1FAIpQLSfkxh1w6vK8fLYwAbAAEVhvhMAJwfFNDtYtPUVk1y5WTHvJmQ/viewform In this case, we will go ahead and file an autofill report for you with the information you added here. In the future, if you encounter any other page or app that doesn't autofill as expected, please avoid opening a new GitHub issue and go directly to the corresponding form. This issue will now be closed. Thanks!
Author
Owner

@derei commented on GitHub (Aug 20, 2024):

@Greenderella it feels a bit strange (read it as uncomfortable) to see you're using google forms for such tasks, for several reasons:

  • people opting for Bitwarden may not want to use Google services at all, or just the bare minimum (or else they could simply use google for password management)
  • google forms require authentication with a gmail address, which more than often can be different from the one used in Bitwarden (and maybe I don't want to disclose more than I already have)
  • the google forms filling system is not obvious to users encountering (autofill) issues, therefore the request for us to fill such issues that way, can appear unreasonable.

So, this choice of your team to rely on Google, not only questions Bitwarden internal privacy philosophy, but also external (towards the app and its users), but it also puts the users wanting to report such issues, in an inconvenient position.

Whilst this comment is off-topic, I believe it should be granted an answer, because it concerns most if not all of Bitwarden users.

Thank you.

@derei commented on GitHub (Aug 20, 2024): @Greenderella it feels a bit strange (read it as uncomfortable) to see you're using google forms for such tasks, for several reasons: - people opting for Bitwarden may not want to use Google services at all, or just the bare minimum (or else they could simply use google for password management) - google forms require authentication with a gmail address, which more than often can be different from the one used in Bitwarden (and maybe I don't want to disclose more than I already have) - the google forms filling system is not obvious to users encountering (autofill) issues, therefore the request for us to fill such issues that way, can appear unreasonable. So, this choice of your team to rely on Google, not only questions Bitwarden internal privacy philosophy, but also external (towards the app and its users), but it also puts the users wanting to report such issues, in an inconvenient position. Whilst this comment is off-topic, I believe it should be granted an answer, because it concerns most if not all of Bitwarden users. Thank you.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/android#1976