mirror of
https://github.com/dani-garcia/vaultwarden.git
synced 2026-03-02 22:57:18 -05:00
Autofill on page load field dashed out on Browser Extensions caused by ios Mobile app #2151
Labels
No labels
SSO
Third party
better for forum
bug
bug
documentation
duplicate
enhancement
future Vault
future Vault
future Vault
good first issue
help wanted
low priority
notes
question
troubleshooting
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/vaultwarden#2151
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
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?
Originally created by @Gerardv514 on GitHub (Jan 24, 2025).
As discussed in #5388 I am noticing when viewing vault items in the Chrome Browser extension, the field called "Autofill on Page Load" is completely blank. If I open the browser extension and click the + add sign, I see the extension automatically completes this field with a default of "Use Default Setting."
I believe these entries of null/blank happen, when you save a new vault item from the mobile apps, since I can reproduce that on demand. I am specifically using ios mobile app.
I also just tried to reproduce this using Bitwarden cloud, and it doesn't happen there.
My question is, forall the items that are blank (or probably null), isthiscaused by adding vault items fromsome other BW app such asthe mobile ios app,or could it be the prompt in a browser after logging into a site for the first time and then clicking yes to save?It may not be an issue now, but seeing how the mobile apps have become more strict with the ways things are saved, could this cause an issue down the line? I am using a sqlite3 database, according to the data folder, can anyone recommend a sqlite3 viewer for Windows and then where in the database can I find this field.
In the below example, you will see how my existing item is saved into the vault which is blank/null for auto fill on page load field. This item was saved either two ways, through ios mobile app or Chrome Extensions using the pop up of "Do you want to save this item," and it was created sometime back in 2023. Yet if I try and add it using + sign (add) in chrome extension if populates this field with default setting.
I am on latest 1.32.7, for the sake of it I did check my test container as well and same result there.
I have actually noticed this null/blank field ever since using Vaultwarden, and in 2021. I actually have an email where I wrote this up to Bitwarden support, but after learning more of the difference of Vaultwarden & Bitwarden apps at the time, I let that discussion fizzle out when they said they couldn't reproduce. In retrospect with more experience now, I should have started the discussion here.
Attempting to look at this in the DB. I created two different test login items, one was created using mobile ios app, and the second was created using the bitwarden chrome browser extension. All I filled in was item name. After saving, On the chrome extension I viewed both test items and I see one that has the Auto Fill on Page load filled out (showing the default option to use in options) and the 2nd one (created from ios app) auto fill on page load is completely blank.
{"autofillOnPageLoad":null,"password":null,"passwordRevisionDate":null,"totp":null,"uris":
{"password":null,"passwordRevisionDate":null,"totp":null,"uris":
Existing item saved into the vault (Chrome Extension)
If I click + add item, in the Chrome Extension, I see the field is automatically completed.
Originally posted by @Gerardv514 in https://github.com/dani-garcia/vaultwarden/discussions/5388
@stefan0xC commented on GitHub (Jan 25, 2025):
I'm not sure I understand the issue. Do you want it to be displayed as
Use default settingsif the value has not been set? (As it's seemingly done in the items in the vault overview?)I mean either way this seems like a client issue to me.
@Gerardv514 commented on GitHub (Jan 25, 2025):
Using chrome browser extension and using iOS mobile app.
When adding an item thru chrome browser extension the field for autofill is filled in by default (use default settings - from options).
When adding an item from iOS mobile app that field is blank.
I understand it maybe a possible client issue, but when I do this using bitwarden cloud, which is add an item to vault using iOS mobile app and then when viewing that item from chrome browser extension, that field is set to use default settings - from options.
Since the mobile app is somehow either sending that data by default to the cloud server or the server auto fills it in I am not sure but I would imagine that is where Vaultwarden doesn't mimic the behavior.
@BlackDex commented on GitHub (Jan 25, 2025):
For me the Bitwarden Cloud Vault behaves in the exact same way as you described.
It returns
"autofillOnPageLoad":nullLooking at your screenshots, you seem to have an older version of the extension i think, since for Chrome the latest version is Version: 2025.1.1 SDK: 'main (28c7e29)', and that has the new look and probably some fixes for the issue you have.
Since there is no difference in what Vaultwarden returns and what Bitwarden Cloud seems to return I'm going to close this.
@stefan0xC commented on GitHub (Jan 25, 2025):
I think there is a difference as the Bitwarden server seems to always return more values for the
datathan we do:Whereas Vaultwarden only returns a bare minimum (e.g. with an entry that was created via the Android app that has
{}in thedatacolumn in thecipherstable):@BlackDex commented on GitHub (Jan 25, 2025):
I was more referring to the specific field mentioned.
Most of those fields are optional, even in the new Mobile clients.
So the can be omitted or have a
nullvalue.Vaultwarden basically only returns the value's sent by the clients them self. Vaultwarden does no checking for missing or new fields to stay compatible with newer features automatically, as far as that is possible of course.
@Gerardv514 commented on GitHub (Jan 25, 2025):
I believe with this, if you look in the chrome extension ui, even if it is null it will display in the chrome extension as default as in options.
It is when autofillonpageload is completely missing and not indicated, is when in the chrome ui it is displayed as blank.
I had noticing so long as autofillonpageload was put in to the db, the field on chrome extension is completed as default setting in options, even if the value was null attached to autofillonpageload.
I also have the new extension ui since it was released sometime after the discussion was started and is the same result. This is also not an extension problem because again as I indicated earlier I see two different ways this can be stored in the database. The entries that have autofillonpageload:null show up in chrome extension. The entries that do not have this value at all in the db show as completely blank in the chrome extension.
@Gerardv514 commented on GitHub (Jan 25, 2025):
Exactly what I think I was coming to the conclusion with. Considering bitwarden cloud returns/or has that autofillonpageload line, the chrome extension will have that field filled out and completed.
Because Vaultwarden doesn't even mention/return the autofillonpageload, that causes the extension ui to show completely blank.
So again even in cloud, with that value being null, it shows in ui as default as set in options.
@BlackDex commented on GitHub (Jan 25, 2025):
That item I created a screenshot with was created via the Android client. So if the iOS client does not do that, it is probably a bug on the iOS client side i think. Not that Bitwarden will fix that, since they are probably fixing the request/response anyway i think.
@Gerardv514 commented on GitHub (Jan 25, 2025):
How could it be the iOS client if it doesn't do that in bitwardens cloud instance?
The item you created via android client, was that against the Bitwarden cloud or Vaultwarden?