Passwords missing from share sheet 1Password

k8user
k8user
Community Member

Suddenly my logins and their passwords don't appear on either my phone or iPad when I use the share sheet 1Password. My credit cards and identities are there but that's all. If I go to the app (iOS) everything is as it should be.

Comments

  • AGAlumB
    AGAlumB
    1Password Alumni
    edited April 2016

    @k8user: Sorry for the confusion! The 1Password extension will only offer you logins for the current URL. So for example, if you're at 1password.com (or no website is loaded at all), you won't be offered logins for agilebits.com in the extension. I hope this helps! :)

  • k8user
    k8user
    Community Member

    Weird, just noticed it.
    But- occasionally a "please register" page has an entirely different url than the actual site so the password is not available to the login page. So, I guess that's what "search" is for!
    Thanks for cling me in!

  • littlebobbytables
    littlebobbytables
    1Password Alumni

    Hi @k8user,

    It's a tricky one. The registration pages can be very different and in some cases may not be what you want the Login item to be based on but it's the first page where the details you want stored will exist. I haven't created many Login items on my iOS device as I use my Mac more but even then, what I've always done there was to register, log out and then create the Login item based on the actual login page for the site. It's never felt onerous to me but I can understand why others would disagree. We do our best of course to make sure 1Password is intelligent enough to use the details from the registration page on the login page and we're always doing our best to improve this :smile:

    If you're finding a particular Login item isn't appearing when you visit the login page for the site one thing to consider is copying the required URL to the iOS clipboard and adding it as a second website field to the Login item. Of course you will want to make sure the URL and page are legitimate as they URLs for a registration and login page shouldn't differ that wildly given what we match is the Fully Qualified Domain Name (FQDN) e.g. accounts.google.com.

This discussion has been closed.