Generated passwords not always appearing in 1Password application

chellman

I've seen this issue periodically since the big Safari 5.1 related upgrades to 1Password. Sometimes when I generate a password for a site, 1Password will guess incorrectly which of the fields I've filled out (usually email versus username on a Drupal site) is the one that should be used as the canonical username (it usually guesses email instead of name).



This not a problem - I just go into the 1Password application and edit the new password. Problem is, the new password is not always there. This just happened again, so I'm reporting it. I generated a password on a website and saved it as a regular login after I used it, and neither the generated password, nor the full login, are available in the 1Password application. They do seem to be saved, because I can see them in the Safari 5.1 extension, but not in the main application.



I've tried clearing the 1Password cache in Help > Troubleshooting, but it hasn't solved the issue. Is there anything else I can do? It seems in the past that waiting a little bit, or frequent relaunchings of 1Password (or maybe Safari, I don't know) has done the trick, but in 10 minutes or more since this happened, that doesn't seem to have done the trick yet.

[Deleted User]

Hello chellman,



First of all, any generated passwords should show up in your Generated Passwords (GP) vault, which, for those readers who do not know, is located directly above Trash icon in the 1Password application. This applies to generated passwords created within the 1P app or the 1P extension for any browser. If you do not see the GP vault, you can enable the icon in 1Password > Preferences on the General tab. Make sure the "Generated Password" checkbox is selected.



So, just to be clear that I understand your issue, I want to restate the problem: Generated Passwords created in Safari 5.1 do not show up in the GP vault in the 1Password application. Please let me know if I misread.



Presuming I understood you, will you please confirm/deny if you are running the latest [b]beta[/b] versions of 1Password and 1P's Safari extension? As of this typing, the current [b]beta[/b] versions are 3.8.1 (build 31115) & 3.8.1.b1, respectively. We did have an issue where changes made within the desktop app and/or the extension were not reflected in the other, but that problem was addressed in an earlier release.



If you are still experiencing this behavior while running our latest [b]beta[/b] releases, I recommend uninstalling the Safari extension and then closing Safari using the Cmd-Opt-Q shortcut. Next, quit the 1Password application if it is open. Finally, restart the 1Password application and follow the Safari installation prompts.



Please let us know if you continue to see generated passwords not showing up in the 1P app. If you still do, we'll need to investigate.



Cheers!



Brandt

chellman

Thanks, Brandt.



I am aware of the separate between GPs and regular logins -- I wasn't seeing them in either place. As expected, it was eventually fixed, which makes me think the cache is to blame, even though clearing it manually didn't seem to work for me.



I am currently running the latest release versions of 1P and the 1P extension. If this issue is one that the beta solves, I'm willing to jump in on that.

[Deleted User]

Hello chellman,



Thank you for confirming. I've learned never to assume, no matter how much I may believe I understand. <img src='http://forum.agilebits.com/public/style_emoticons/<#EMO_DIR#>/smile.png' class='bbc_emoticon' alt=':)' />



I'm glad the issue is now fixed for you as of now. There was a problem with a previous release where the 1Password Agent process was not syncing the 1P app with the extension. That would have created the behavior you described.



Currently, I am running 1P 3.8.1 (build 31115) & 1P's Safari beta extension 3.8.1.b1, and I do not experience the issue. If you ever experience the problem again, please try those versions. Hopefully, you are good to go now, and you will not see that problem again.



Cheers!



Brandt