Mess with 1Password7 and iCloud

Options
JamesLamb
JamesLamb
Community Member
edited April 2022 in Lounge

This is my first time posting, because I'm usually able to resolve these issues myself. But, this one has got me. My Mac desktop app, version 7.9.4, is syncing with my online 1password account. However, my iOS app, which is logged in tot he same account, is syncing to the iCloud. The vaults have different names, with the desktop version being my "personal" vault. However, iOS has its own synch destination, which it calls "primary." I cannot figure out a way to get everything to play nice; i.e., my iPhone is doing its thing with iCloud and my desktop app is syncing with the 1Password online account.

I will also add that every item in my iPhone app appears twice, something that happened once I upgraded from a legacy 1Password account to the new subscription scheme.

I tried to figure out a way to have my phone app sync with the 1password account directly and not iCloud, but I can't see a way. Also, I now have a whole bunch of data on the phone I don't want to lose.

Any help would be much appreciated. Thanks.


1Password Version: 7.9.4
Extension Version: Not Provided
OS Version: Mac OS 12.2.1, iPhone 11 IOS 15.3.1

Comments

  • Hi @JamesLamb:

    Thanks for reaching out! I can definitely understand how seeing multiple copies of your data is frustrating. Given that it sounds like you might still need to migrate some of your data to your 1Password account, getting in touch with our migration specialists via email would be your best bet. Please send an email to support@1password.com summarizing the trouble you're having, and include a link to this thread: https://1password.community/discussion/128860/mess-with-1password7-and-icloud#latest as well as your username: JamesLamb.

    After you email in, you'll receive a reply from BitBot with a support ID that looks something like [#ABC-12345-678]. Post that here, and I'll be able to connect the dots and make sure your email gets to the right place.

    Jack

This discussion has been closed.