This is a staging forum for AgileBits, not an official support forum. Visit http://discussions.agilebits.com instead.

MAS (3.9) not reloading keychain properly

The first time it happened I assumed it was a fluke... but the second time...



My MAS version of 1password has twice failed to notice changes to the keychain file that I made while on my windows machine. I confirmed the keychain files were good (i.e. contained my changes) using "1Password Anywhere" feature of loading the html/javascript embedded in the keychain.



I quit and reloaded 1password multiple times and still couldn't get it to notice the new/updated entries.



So far the only thing I've been able to do to force it to reload the keychain is to use the "stop using dropbox" and then "use dropbox" option in the preferences. I haven't tried a full system reboot, though I imagine that would work too.



Here's my setup:



1password for windows 7 (gaming desktop)

1password (MAS) for 10.7.1 (desktop)

1password 3.8.x for 10.6.8 (laptop)

1password for iphone (iphone4)



The only version that has had trouble is the MAS version.

Comments

  • Ben
    Ben AWS Team
    Hi elvaen,



    Can you please verify that changes to other files on Dropbox are properly syncing to the computer in question?
  • Here is a quick "bug" report, if u uninstall the non-MAS version by just moving the .app to the trash, once u install the MAS version the Safari extension will not work, u also have to uninstall the extension a re-install it.
  • Hi bwoodruff,



    Yes, I confirmed that dropbox was syncing everything properly by using the "1Password Anywhere" feature on the computer with MAS-1password installed. Loading the keychain in a browser had all the new/modified entries I had created on windows.



    I've had no issues with the sync happening in the other directions. i.e. if I author new changes in the MAS-1password the other clients pickup the changes without any issues.



    I wish I could reliably reproduce the problem for you, but so far it seems intermittent.
  • Ben
    Ben AWS Team
    Thank you for the additional information. We'll try to track this down. Thanks for the report.
  • elvaen
    edited September 2011
    Hi Ben,



    I'm sorry to say this problem is worse than I originally thought. Now that I've spent some time testing it I can say that it is 100% reproducible; more concerning though is that it appears to be possible to partially corrupt the 1password database.



    To reproduce:

    1) Create a new generated password on your windows client named "testsync1"

    2) wait for dropbox to finish syncing (takes mere seconds)

    3) switch to your Mac with MAS-1password and note that the changes do NOT appear

    4) open keychain with "1password anywhere" in safari and you can see the changes.



    To cause keychain corruption:

    [i](this corruption is repairable with "Repair Keychain" menu option on the windows client, but this option seems to be (inconceivably!) missing from MAS-1password??)[/i]

    5) On MAS-1password create a new generated password called "testsync2"

    6) open keychain in 1password anywhere and now only "testsync2" shows up.

    7) 1password windows now shows "testsync1" and "testsync2"

    <img src='http://forum.agilebits.com/public/style_emoticons/<#EMO_DIR#>/emoticon-0103-cool.gif' class='bbc_emoticon' alt='8)' /> On 1password windows create another generated password called "testsync3"

    9) Back on MAS-1password you'll still see only "testsync2"

    10) Open keychain in 1password anywhere and now you'll see "testsync2" and "testsync3"

    11) On MAS-1password create a new generated password called: "testsync4"

    12) open 1password anywhere and now you'll only see "testsync2" and "testsync4"

    13) back on 1password windows you can still see: testsync1, testsync2, testsync3, testsync4.



    14) Run the "repair keychain" process on 1password windows

    15) 1password anywhere now shows testsync1, testsync2, testsync3, testsync4

    16) MAS-1password still only shows testsync2 and testsync3

    17) Restart your mac (or reload the keychain by toggling dropbox on and off)

    18) MAS-1password now shows testsync1, testsync2, testsync3, testsync4



    If I had to guess I would say that there is some form of an "id" field for these keychain entries and because MAS-1password doesn't get the updates made in other clients MAS-1password iuses the same ( [i]id.next()?[/i] )for the new entry. 1password anywhere seems to use this newer entry in the case of duplicate ids. The repair process appears to properly resolve the id issues and restore sanity to the keychain.
  • elvaen
    edited September 2011
    I just found an easier way to convince 1password to reload the keychain:



    Uncheck "Keep Helper Running to enable extension features".

    Quit 1Password

    Relaunch 1Password and the updated items properly show up.



    However, in light of the above issues with MAS-1Password (which I would rate as extremely critical) I've decided to remove MAS-1Password and reinstall 1Password 3.8.6.
  • Ben
    Ben AWS Team
    Hi elvaen,



    I'm sorry to hear about the troubles you are having. Unfortunately we have not been able to reproduce this issue.



    The first thing I would suggest is reinstalling the Safari and Firefox extensions (if installed) on your 3.9 machine.

    [url="http://help.agilebits.com/1Password3/troubleshooting_safari_5.1.html#extension_data_does_not_match_the_main_application"]Extension Data Does Not Match the Main Application[/url]



    Failing that, could you please let us know, specifically, what versions of:

    1Password (on each machine)

    the 1Password extensions (in each browser)

    and Dropbox (on each machine)



    you are using?



    Hopefully if the above does not resolve the issue for you, with the above information we can reproduce the issue and track it down.



    Thanks!
  • elvaen
    edited September 2011
    Hey Ben,



    I only use Chrome, but I went ahead and reinstalled the Chrome and Safari extensions (firefox is not on my computer), but I'm still seeing the same behavior. In fact I'm still getting the same behavior with 3.8.6 as well. Essentially 1Password on my Lion machine is not automatically reloading the keychain file when dropbox updates the keychain. 3.8.6 is a little easier to deal with because I can either restart the app or use



    Menu > Help > Troubleshooting > Restart Agent



    Which seems to work to force reload the keychain. It makes me a little nervous though because if I don't reload the keychain manually and start making updates in the Lion 1Password things seem to get all out of whack and I have to "Rebuild Data File" to get the data to be consistent again.



    I also have a 10.6.8 laptop running 3.8.6 and have no issues with sync updates on that machine or on my windows machine.



    MacPro (early 2008) running 10.7.1 and 1Password 3.8.6 with Dropbox 1.1.45

    MacBook Pro running 10.6.8 and 1Password 3.8.6 with Dropbox 1.1.45

    Windows 7 64bit with 1Password 1.0.8.217 with Dropbox 1.1.35



    Changes made on lion show up immediately in the other computers.

    Changes made on windows or my laptop do not show up in Lion.



    On a lark I used disk utility to repair a few permissions on Lion, but it didn't resolve these issues either.



    In case it's helpful to know: I -just- upgraded my MacPro to Lion and did so by completely wiping my hard drive and doing a clean install of Lion.



    Thanks for your help...
  • Ben
    Ben AWS Team
    Hi elvaen,



    Stu and I have been unable to track this down, but I've shared the case with the rest of the team. Hopefully if we get another set of eyes on this we can figure out what is going on.



    Thanks

    Ben
  • brenty
    edited September 2011
    Hey there, elvaen! I am sorry for the trouble.



    Could you please send us a Diagnostics Report for each machine to help us track this down? You can generate one in 1Password on your Mac by going to Help > Troubleshooting > Diagnostics Report... in 3.8.6, or using our standalone [url="http://cdn.agilebits.com/dist/1P/mac/util/1PasswordTroubleshooting.zip"]1Password Troubleshooting tool[/url]. Just save the file and attach it to an email (support at agilebits dot com), and be sure to include any other details or screenshots you can as it will help us understand the problem better. Please also include a link to this thread for context. We haven't seen other cases of this, so right now you are our only source of data on the problem.



    Please let me know. I look forward to hearing from you. <img src='http://forum.agilebits.com/public/style_emoticons/<#EMO_DIR#>/smile.png' class='bbc_emoticon' alt=':)' />



    [quote name='elvaen' timestamp='1316648346' post='50954']

    Hey Ben,



    I only use Chrome, but I went ahead and reinstalled the Chrome and Safari extensions (firefox is not on my computer), but I'm still seeing the same behavior. In fact I'm still getting the same behavior with 3.8.6 as well. Essentially 1Password on my Lion machine is not automatically reloading the keychain file when dropbox updates the keychain. 3.8.6 is a little easier to deal with because I can either restart the app or use



    Menu > Help > Troubleshooting > Restart Agent



    Which seems to work to force reload the keychain. It makes me a little nervous though because if I don't reload the keychain manually and start making updates in the Lion 1Password things seem to get all out of whack and I have to "Rebuild Data File" to get the data to be consistent again.



    I also have a 10.6.8 laptop running 3.8.6 and have no issues with sync updates on that machine or on my windows machine.



    MacPro (early 2008) running 10.7.1 and 1Password 3.8.6 with Dropbox 1.1.45

    MacBook Pro running 10.6.8 and 1Password 3.8.6 with Dropbox 1.1.45

    Windows 7 64bit with 1Password 1.0.8.217 with Dropbox 1.1.35



    Changes made on lion show up immediately in the other computers.

    Changes made on windows or my laptop do not show up in Lion.



    On a lark I used disk utility to repair a few permissions on Lion, but it didn't resolve these issues either.



    In case it's helpful to know: I -just- upgraded my MacPro to Lion and did so by completely wiping my hard drive and doing a clean install of Lion.



    Thanks for your help...

    [/quote]
  • Hey guys, I sat down tonight to grab a few Diagnostic reports both before and after the sync issue/duplicate entries which have in the recent past required I use the rebuild option...



    As Murphy's Law would have it, I'm unable to reproduce the issue tonight. Everything is syncing properly into my "Lion 3.8.6" from both my "Snow Leopard 3.8.6" and my "Windows 7 1.0.8.217" copies of 1Password.



    I'm going to go ahead and send a diagnostic report anyway since there's still one item in there that is confusing to me. If I can reproduce this again in the near future I'll let you know...
  • Ben
    Ben AWS Team
    [quote name='elvaen' timestamp='1317104287' post='51415']

    Hey guys, I sat down tonight to grab a few Diagnostic reports both before and after the sync issue/duplicate entries which have in the recent past required I use the rebuild option...



    As Murphy's Law would have it, I'm unable to reproduce the issue tonight. Everything is syncing properly into my "Lion 3.8.6" from both my "Snow Leopard 3.8.6" and my "Windows 7 1.0.8.217" copies of 1Password.



    I'm going to go ahead and send a diagnostic report anyway since there's still one item in there that is confusing to me. If I can reproduce this again in the near future I'll let you know...

    [/quote]



    Great! Thanks. <img src='http://forum.agilebits.com/public/style_emoticons/<#EMO_DIR#>/smile.png' class='bbc_emoticon' alt=':)' />
  • doone128
    edited September 2011
    I had this today also. I created a new login on my Windows machine and when I tried to login to the site some 7 hours later on my mac, the 1Password extension was not aware of the login.

    I got around it by opening the 1Password App and logging in. The login then appeared in the 1Password app and extension. Could this be something to do with universal unlock?
  • Ben
    Ben AWS Team
    [quote name='doone128' timestamp='1317166761' post='51509']

    I had this today also. I created a new login on my Windows machine and when I tried to login to the site some 7 hours later on my mac, the 1Password extension was not aware of the login.

    I got around it by opening the 1Password App and logging in. The login then appeared in the 1Password app and extension. Could this be something to do with universal unlock?

    [/quote]





    I use Universal Unlock without any such problems, but if you could help us track this down, that would be much appreciated. Can you try disabling Universal Unlock and attempt reproducing the symptoms you described?
  • When I was having these issues I tried all sorts of different settings including enabling and disabling the universal unlock and it didn't have any effect.



    The 1Password Helper (MAS) and 1Password Agent (3.8.6) both just failed to notice the changes to the keychain files; maybe even a bug in Lion failing to send the agent/helper whatever event it's listening for.



    Either way I'm willing to bet that doone128 is on 10.7.1 (Lion); am I right doone?
  • I am indeed on 10.7.1. Had a busy day today so haven't had time to test but I'll try and reproduce the issue tomorrow and report my findings here.
  • Hey there, doone128! Thanks for following up. Could you try restarting your Mac? If you are still having trouble, Could you please send us a Diagnostics Report? You can generate one using our standalone 1Password Troubleshooting tool:



    http://cdn.agilebits.com/dist/1P/mac/util/1Password%20Troubleshooting.zip



    Just attach this to an email (support at agilebits dot com), and be sure to include any other details or screenshots you can as it will help us understand the problem better. Please also include a link to this thread for context.



    Thanks in advance! <img src='http://forum.agilebits.com/public/style_emoticons/<#EMO_DIR#>/smile.png' class='bbc_emoticon' alt=':)' />
  • Brenty - just tested this again and it worked without issue. Bizarre. I'll keep testing it and run the diags if I hit the issue again. Thanks!
  • Thanks for the update, doone128!