Autofill NOT working

mpollock
mpollock
Community Member
edited May 21 in 1Password in the Browser

I just tried accessing a Chase account with autofill and nothing I did got the Chrome extension to autofill. had to manually cut and paste the data into the fields.


1Password Version: Not Provided
Extension Version: Not Provided
OS Version: Not Provided
Browser: Not Provided

Comments

  • Hello @mpollock! 👋

    I'm sorry that you're unable to fill your login into the Chase website. Chrome on the iPhone and iPad doesn't support extensions, instead 1Password relies on iOS itself to detect and fill fields using a technology developed by Apple called iOS Autofill.

    When you tap on the username or password field on the Chase website do you see "Passwords" appear above your keyboard? If you don't then I would like you to make sure that you have turned on AutoFill to work with 1Password:

    1. On the Home screen, tap Settings.
    2. Tap Passwords > Password Options.
    3. Turn on AutoFill Passwords and Passkeys.
    4. Select 1Password.

    Then try to fill your login again using this guide: Use 1Password to fill and save on your iPhone and iPad

    If that still doesn't work then can you try to fill your login into the Chase website in Safari, not Chrome? Does AutoFill work in Safari?

    -Dave

  • mpollock
    mpollock
    Community Member

    Hi Dave and thank you for your reply. Actually I am on a Chrome OS desktop and use 1Password success all day everyday for years. For some reason this website, even after reloading the page, will not allow 1Password to fill in.

  • Dave_1P
    edited May 21

    @mpollock

    Thank you for clarifying that you're using ChromeOS, I've moved your post from the iOS category to the 1Password in the browser category. 🙂

    Our developers are aware of an issue where 1Password in the browser isn't able to detect and fill fields on Chase.com. They're currently working on a fix and, for the time being, copying and pasting your login information is the best workaround.

    I'm sorry for the inconvenience.

    -Dave

    ref: dev/core/core#2900

  • mpollock
    mpollock
    Community Member

    Great. My apologies for making the post in the wrong section. I am happy to hear it is a known issue and is being addressed.
    Cheers,
    Mark

  • No problem at all, @mpollock. Let us know if there's anything else we can assist you with. 🙂

    -Evon

This discussion has been closed.