1Password update failed due to two attached clone drives!?
The most recent update to 1password failed because I have two attached cloned drives which obviously have 1password on them because they are clones. I do not understand how they can conflict with 1password on my main HD and why an update to 1password on my main HD should consider them? What should I do? Disconnect the clones before updating 1password from now on? This is the only app where I have seem this problem and 1password seems to be behaving normally other than the update failure.
1Password Version: 5.4.3
Extension Version: 4.4.4
OS Version: 10.11.2
Sync Type: Dropbox
Referrer: forum-search:My most recent update failed due to having 1password installed on my attached cloned drives?
Comments
-
-
1Password is not the only app that does this. The App Store, for instance, will offer to update things on external drives, as will older versions of Office. The simplest way to get around this is to disconnect your clones while you're doing updates.
0 -
Once you remove the additional copies of 1Password (or disconnect your cloned drives) 1Password will update properly for you.
The problem here is that the operating system can get a bit overzealous when it is searching for 1Password mini. Sometimes it finds a mini that is stored in a 'unique' location, instead of looking first in the appropriate location. We've even seen cases of it finding a version of 1Password mini on backup drives. If the incorrect version of 1Password mini launches, 1Password will not run correctly. We're not sure that there's anything we can do to alleviate this problem (since the OS is the one looking for 1Password mini) but we are searching for alternative solutions.
In the meantime, we strongly recommend keeping only 1 copy of 1Password on your system. If you ever need to reinstall 1Password for any reason, you can snag a fresh new copy from our downloads page, no need to keep a backup copy on your system.
I hope this helps, but we're here if you have any further questions or concerns!
0 -
I have this issue too. I'm glad to hear Agilebits is aware of it. However, I'd like to point out this is a new issue -- at least new to me. I've used 1P for many years and have never seen this particular issue until very recently. I only have ONE copy of 1P and 1P Mini on my computer. The message always relates to copies of the app on my backup clone drives. It would be a real pain to have to unmount my two backup drives every time there's an update to 1Password.
0 -
Is there any way to manage the OS search field?
0 -
@AMCarter3 there are two potential ways to managed the problem. The recommended solution (if you wish to have the backup drive permanently connected) is to:
- delete any copy of the 1Password app file (only) from the backup drive; and
- exclude the 1Password app file from any further backups (because, of course, you can always re-download it if you need to).
Provided you don't use any app cleaner tool when deleting the app file none of this will interfere with your 1Password data.
Others have reported that disabling Spotlight indexing of the backup drive also solves the problem.
Is there any way to manage the OS search field?
Sorry, if you know this already but if you mean managing the Spotlight search and excluding the backup drive, you can do that by going to System Preferences > Spotlight and then the Privacy tab.
Stephen
0 -
Thanks, Stephen. Since my two clone drives are backed up every other night using SuperDuper, option 1 and 2 do not make sense. But, excluding my external backup clone drives from the Spotlight index search is a perfect solution... I'll try it. I think it will work because one of my clone backup drives is already excluded from Spotlight indexing and it does not show up in the list of drives when updating 1P.
0 -
It is possible (details in another thread, or check the manual) to exclude items from a Super Duper backup.
Also, if the external drives aren't encrypted, SuperDuper will just mount the clone drive if it is unmounted at the scheduled time, so you can just leave the drive unmounted.
0 -
Hi @AMCarter3,
As @danco mentions, it's possible to setup exclusions in Super Duper. We recommend the Exclusion approach.
While removing the clone drives from Spotlight might be a good idea in general, it may or may not solve the issue when updating 1Password. If it does solve it, it's not guaranteed to be a permanent solution. 1Password asks the system for the list of apps 1Password apps installed on the system. There's no guarantees that the system uses Spotlight to achieve this.
It's a bad idea to have more than one instance of 1Password on your Mac, even if on a backup drive. Maybe you've been lucky in the past and have had no issues. This is the number one source of issues for our users. The system ends up getting confused about which 1Password mini it should launch, and bad things happen.
The warning during updates are just that, warnings. You can click 'Continue' to ignore the warning. We recommend you not, but ultimately it's up to you to decide.
We may add a check like this to the start up of 1Password in the future to warn you if you have multiple instance on your disk. Again because you're likely to run into issues eventually.
Setting up an exclusion in Super Duper or your backup tool of choice is really the best way to go here.
I hope this helps.
Rick
0 -
By the way, I chatted with Dave Nanian, SuperDuper (SD) developer, today about this issue. He offered a BETTER SOLUTION. You will want to try this -- it works and it's easier than using SD's script to exclude 1Password from clone copies.
All you need to do is set the “On Successful Completion” option for a backup to “Eject clone” upon completion. When SD quits (or you quit it manually), the external drives automatically EJECT themselves. When you turn SD back on to do a manual backup, the external drives automatically remount for the backup, and then again, eject after the backup is completed. This way the the drives can remain connected and will automatically remount for the next round of backups.
Try it. It works.
0 -
That's a great recommendation, @AMCarter3. Thanks!
Rick
0 -
The auto-eject / auto-remount of a clone backup drive seems to work fine. I've tested both manual and scheduled backup's with SuperDuper. Interestingly, this method of setting up SuperDuper should not only avoid the issue with 1Password getting confused about which app to update, it should also reduce spinning wheels related to waiting for an attached backup drive to spin up.
The only caveate I can think of is when a backup drive has a partition for a clone backup AND another partition for Time Machine backups.
0 -
Thanks for the update. I hope this helps others too. :)
Rick
0 -
Please pass this tip along to your colleagues at Agilebits. If this is really a common issue for a lot of 1Password users, all of the support folks at Agilebits should know about it. (No one seemed to be aware of this method when I asked. )
0 -
0
