iOS extension ignores secondary website field

rappjo
rappjo
Community Member

Hello,

It seems like the secondary website field on the iOS app is ignored. So if I am on a website with a password I want to fill and it matches the secondary website, it won't show up as a fillable password and in order to log into the site I have to pull up the app rather than the extension. Is this intended behavior?

Comments

  • Hi @rappjo,

    Thanks for taking the time to write in. That should not be the case. Is this only happening with a few items, or all of them?

    Also, what version of the app do you have?

    (iOS) How to keep 1Password up to date

    Thanks.

    Ben

  • rappjo
    rappjo
    Community Member

    I had the latest as of yesterday (6.4), just updated to the latest as of today (6.4.1). I was seeing this issue with a login that's shared between Google Apps and Okta.

  • AGAlumB
    AGAlumB
    1Password Alumni

    @rappjo: Ah, that makes sense. Does 1Password fill either form correctly? It sounds like the login may have been saved on one, and if the other is substantially different 1Password won't be able to fill it the same way.

    If you can tell us the URLs in particular you're having trouble with we'll be happy to test them and try to offer a solution, workaround, and improvements in the future!

    That said, in many cases manually saving a new login for the site will allow 1Password to save additional information from the form (even better using the 1Password browser extension on the computer, if that is an option for you). Just try these steps:

    1. Navigate to the website
    2. Enter your login credentials
    3. Tap the 'key' icon (or the Share button, to use the extension in Safari) to bring up the login menu
    4. Tap + New Login
    5. Tap Save
    6. Close the webpage and tap the URL in your new login item to have 1Password fill it
    7. Tap the "Sign in"/"Log in" button to submit the form

    Please let me know how it turns out. I look forward to hearing back from you. :)

This discussion has been closed.