1Password 4.1 Losing Sync Permissions after System Restart [MAS] - resolved with 4.1.2 update


Team Member
edited March 2014 in Mac

If you purchased 1Password 4 from the Mac App Store, please be aware that we are currently tracking down a bug that can cause 1Password to lose permission to sync after a system restart. This seems to happen more frequently to non-primary vaults that are synced to a location other than the default, but we have seen cases of primary vaults failing to sync as well.

As @dteare has mentioned, we suspect this is related to Apple's sandboxing regulations:

The security scoped bookmark is needed in the Mac App Store version because of the sandboxing feature. This bookmark is given to us by OS X when you select the folder (you may have heard this called a Powerbox) and we keep this bookmark for later use. For some reason when we try to persist and restore this bookmark it fails.

We've tried everything we can to fix it on our end and believe it may be a bug in Apple's OS X Sandbox code. We've submitted a bug report to Apple in hopes that they can either confirm it's on their end or ours.

Unfortunately, right now we don't have a time frame for when we might have a fix for this.

In the meantime, you have a couple of options:

  1. After you restart your computer, you can disable sync in 1Password and re-enable. Re-enabling will cause all items to sync back up on that computer. This will maintain until the next system restart.

  2. You can switch to Wi-Fi sync if you're only syncing with another iOS device. Or use iCloud if you're syncing to other computers (except Windows).

We very much appreciate your patience. We know how important syncing is, and we're doing all we can to get things working smoothly again as soon as possible!


All our tests suggest that this issue has been resolved with the 4.1.2 update. If you have experienced this bug in the past, please disable and re-enable sync after updating to re-write the permissions.

If sync is still misbehaving for you, please start a new thread or send us an email at [email protected] agilebits .com, we'd be happy to help you get up and running again!

This discussion has been closed.