Version 8 installer won't move past moving data in an empty standalone vault
I was running the 1Password 8 beta on another machine so I have some familiarity with it. On my primary machine, I decided to proceed with the upgrade with the first release. When I launch the installer, it determines I have a local vault and prompts me to move it. I tell it to go ahead and the dialog says "Waiting for data to be moved. Don't quit this app." Nothing happens.
I of course know my standalone vault exists but it is empty. I'm long time 1Password user and I have a Family subscription and use 1Password at work, so a number of cloud vaults as well. I continued to use a standalone (local/primary) vault in 7.x because I wanted a less complex password to open 1Password. (I already have other factors of authentication and security, including a very long password on my 1Password cloud account.)
I thought, "ok, maybe the installers is confused by an empty standalone vault". Not a great start for a first release that has been in beta for quite a while but a simple fix. I launched v7 and added a single dummy record to the standalone vault. Quit, re-tried installer. Same thing.
I'm quite obviously quitting the installer anyway, as it is painfully obvious it's not doing anything with a 0 record local vault for anything over 5 minutes. I know I could safely proceed to go with the "Install without moving data option" and move on with my life (if it works, which I assume it would) but then the scenario here could be lost for testing and feedback purposes.
AgileBits team, please let me know if there is any insight you can provide or information I can provide towards determining the issue here.
p.s. I also tried the posted 8.8.0-11 installer thinking maybe this has since been addressed but same result.
Thanks
1Password Version: 7.9.4 to 8.7.0
Extension Version: not relevant
OS Version: 12.3.1
Comments
-
Hey @brian163 :
1Password 8 does not support standalone vaults which is why you're experiencing the behaviour you've described. This means that you'll need to remove the standalone vault (even if it's empty) in order to successfully complete the installation. If you sign in to your account on my.1Password.com (in a web browser), is your data correct? After you've verified that your data is correct and complete on my.1Password.com, you can remove the standalone vault with the steps outlined here: 1Password - Delete Primary vault.
Let me know how everything goes or if you have any questions along the way.
0 -
I'm sorry, I am not following. What is the purpose of presenting an install dialog that asks about moving your data in a standalone vault to 1Password 8 (which of course would be a cloud vault), if it doesn't "support" standalone vaults (if only to effectively migrate them)?
0 -
For the sake of visually documenting the experience, after clicking "Move Data to Account", this is the window that just sits there indefinitely:
0 -
Well, in the process of taking that extra screenshot I have uncovered what appears to be the bug. When I went to take that screenshot quickly I had launched the 1Password 8 installer again while 1Password 7 was still running. When I clicked on the "Move Data to Account" it presented an additional window asking which of my vaults I want to move the data to:
(My vaults obfuscated for privacy but this is the dialog.)
If I quit the installer and 1Password 7 and launch the 1Password 8 installer alone, this dialog is never presented. I can repeat this behavior.
I don't think most more techie folks like myself would normally run an installer for an existing application upgrade while the existing program is running, nor do I suspect this is really the intended behavior of the installer. But for whatever reason it unveiled the issue of the installer not presenting this window properly on its own.
How does one file a bug report on the installer itself? Or can I entrust the moderators here to relay this issue to the development team? I'd appreciate a response as I will await to move forward with the install so as not to lose any potential debugging information/opportunity.
Brian
0 -
This tripped me up too. I'm glad I found Brian's post with the solution. It's the first app I've used where it wants you to have the old version running when upgrading to the new one. You should include a warning since most people will assume that they need to quit the old one to upgrade
0 -
This content has been removed.
-
This is still happening, by the way.
0 -
I'll close this discussion since it's rather old now but thank you for letting us know that everything is working for you now. 🙂
-Dave
0
