1P5 upgrade problems
Comments
-
I am REALLY VERY UNHAPPY with 1P5 on 10.10.1. First, I purchased the 1P5 upgrade and it went completely berserk with a message that two instances of the application were running. After trying to find all places in the file system where 1P5 had been installed and was causing a conflict with the previous 1P4, I got it running stably again. Next, I installed the Safari extension and all hell broke lose again; at the next restart of Safari (8.02), the application CRASHED HARD EVERY time. Reading through the crash reports, it was the 1PASSWORD5 extension causing the problem. After Safe-starting Safari, removing the extension, and restarting, Safari was still crashing, so something had been done by the 1P5 extension to Safari. In the end, the ONLY fix to get Safari running again (after messing around with disk permissions, safari.plists, blah blah) was a complete OS x 10.10.1 reinstall from the App store. This was on a very well-maintained field system on an SSD in a new MacBook Pro.
Not good enough Agile Bits—not good enough by half. If I did not have so many login passwords registered in 1P5 now, I would be gone to your competitors after wasting a whole afternoon troubleshooting what should have been a minor upgrade. Basically, 1P5 cost me the upgrade price + $300 in wasted time fixing it.0 -
@nekton1 I have split your post from the thread in which you posted because your problem has nothing to do with the original poster's problem in that thread.
I will give you some preliminary answers here but no doubt someone from AgileBits will add comments in due course. (I don't work for AgileBits but am merely a volunteer here.)
- Yosemite gets into a muddle currently if there is more than one version of 1P4 or 1P5 on your disk, or on any disk attached to your computer. That is a problem caused by the Yosemite launch process, not by 1P. You have to ensure that there is only one version of 1P4 or 1P5 on your disk or on any disk attached to your Mac. The usual culprits for duplicate copies are your Downloads folder, Trash or a backup disk attached to the machine. A Spotlight search will help you find any duplicates of course.
- It is very strange that you're reporting such fundamental crashes apparently triggered by the 1P extension in Safari because, so far as I can recall, nobody has reported anything like that here before. There have been reports of difficulties installing the extension in Safari but nothing at all along the lines you mention. Normally with such a severe problem I think AgileBits would ask you to send them a diagnostics report but if you've fixed the problem it's probably too late for that.
Stephen
0 -
Hi @nekton1,
I'm really sorry to hear that you've had such a terrible time upgrading to 1Password 5. We've been looking really hard for a workaround to the Yosemite issue that's causing the issue when multiple copies of the app are installed. So far we've not yet come up with anything. But we're still looking. Ideally Apple would fix the issue that's causing this to happen, but if possible we don't want to rely on that.
As for the issue with the extension in Safari... this is the first I hear of such problems. Did you happen to save any of the crash reports? I would love to get those in front of our browser extension developers to see if there's any bugs that they should be fixing in our extension. What did you see in the crash report that led you to believe it was the extension?
For future reference, you can manually remove all extensions from Safari by following these steps:
- Quit Safari
- Open a Finder window
- Use the Go > Go to Folder... menu item and copy/paste this into the text field it presents:
~/Library/Safari/Extensions/
- Delete all files in this directory
- Open Keychain Access.app from /Applications/Utilities
- Select All Items from the Category sidebar on the left.
- Search for 'Safari'
- You should see an item named 'Safari Extensions List'.
- Select it, and delete it
- Relaunch Safari
Again, I'm really sorry about how terribly this went for you. I'd love for us to do better. If you can provide us with information on those Safari crashes, we may be able to fix up some issues there.
Rick
0