Selecting dropbox folder to sync doesn't work
New install of 1Password on OS X 10.10.1. Just realized that my database is not syncing from Dropbox. Went into preferences, chose the dropbox folder and then the "continue" button does nothing:
My layout is like so:
This reminds me of the behavior I had a few years ago in this thread:
https://discussions.agilebits.com/discussion/comment/86543/#Comment_86543
Syncing is working fine on my IOS devices. I'll validate my other 10.10.1 boxes when I get home. Is this a known issue?
Comments
-
edit : see also post #4 below re: other Macs
Oh boy you have an extremely old quirk. I have not seen this in years.
First lets start off by saying its not a real major issue its just a simple change that needs to be made. I can tell from your screenshot likely you are a Mac user since the days of iDisk ?
The reason I can tell you have been a long time user. Is that the keychain folder on your system is named "1Password.agilekeychain_folder" That has not been used since the days of iDisk. While it will not have affected syncing or your data since that time. ** I fear 1Password 5 is simply not equipped to handle the older setup. **
During the iDisk days, all of us myself included renamed our keychains to include the "_folder" portion. This was a way to trick iDisk into syncing quicker as it processed folders before single files and we wanted our data synced quicker.
What you need to do is rename the Folder from "1Password.agilekychain_folder" to simply "1Password.agilekeychain" All you are doing is removing the "_folder" portion no other part of the file name changes.
The change is straight forward and makes no changes to the internal data portions of 1Password. All it does is tell the keychain it should act as a bundle and not a folder. As a normal safety precaution I would make a backup of your data before proceeding. It should not be needed as I have done this process many times over the years, when helping other just like yourself. With your data its better safe than sorry, so make a backup.
When you rename the folder it will loose its folder appearance and change to a single file looking like this. (see attachment)
Once you do that allow Dropbox to process the change it may be quick OR it could take a brief period of time. Once the sync finishes then try to select the keychain in Dropbox again. Please wait till the sync finishes.
This time you should not have a issue selecting the keychain.
0 -
cc @littlebobbytables - admin
This is an example of how in iDisk syncing... we all changed the keychain name to facilitate faster syncing. We were discussing this in a PM last year about issues you may run across some day.
Since you were in the original thread any chance you can confirm it will still work with the "_folder" in the name.
0 -
This change will likely affect other Macs you may have syncing through Dropbox.
They will be looking for the old location. You for 100% sure will want to verify the setup and for good measure re select the keychain on all machines that are syncing.
0 -
@thightower - Thanks for the tips / instructions but no dice. When I got home I validated that 4 macs at home all running 1password 5 and 10.10.1 are syncing fine with the _folder name. I backed up the data and removed the _folder name. Same behavior trying to select it. If I create a second vault, it will work fine but something about this particular mac and this particular vault is not happy.
0 -
Ended up exporting all my data, blowing it all away from 1password, creating fresh with an import and having 1password 5 create a new sync vault. Bit of a PITA but everything is clean now and syncing again. I suspect my data just had some cruft in it from many upgrades and multiple OS's over the many years...
0 -
Sorry it was acting up. Nice to know they will still work with the "_folder" portion.
Scratches head ???
0 -
Hi @thightower and thank you for the explanation, learning is never a bad thing :smile:
@healy I'm glad you managed to resolve this although I would have hoped we could have found a slightly less drastic solution. Saying that you got yourself up and running again relatively quickly and with no data loss so it's hard to argue with your approach, especially if you're comfortable enough with what you did. You've got to love it when one machine decides to act up when seemingly no different from the x machines playing ball.
0 -
@littlebobbytables - Yes, it was a bit drastic but in the end it fixed the issue. I've been in IT long enough to know that sometimes these gremlins pop up and it's quicker to start fresh than try to track down the how and the why...
0 -
Hey, if it works you can't argue with it :smile:
0 -
I've been in IT long enough to know that sometimes these gremlins pop up and it's quicker to start fresh than try to track down the how and the why...
It took me a long time to get over trying to figure out what had been wrong and move on after finding a fix. Lots of wasted time! Unless it happens again...
0 -
I'm sure there was an (semi) appropriate xkcd strip on this and the different OSes but I can't find it now :(
0
