

A more visible/front page location for item count would reveal that there was a major disparity. Only after I started digging into the issue in Settings>Sync>Items did I realize that more than one or two login items are out of sync. In my case, 29 login items are out of sync (and I don't know which ones without sorting by date). From the cautionary dialog box, the user should then be guided to further information such as a web page which they can then choose to skip if they are in a hurry to proceed to use your app in a read only mode. I suggest throwing up a dialog box saying that "There was a sync error", no matter what the cause, to alert of an issue immediately so I would have at least known to stop inputing new logins and data. Its an issue of reconciling.Įven after I first realized that there were problems logging into a site, I didn't know the disparity between the number of logins in the iPhone vault and Mac vault was so large. In other words this is not an issue of restoring or repairing. That means a headache of reconciling new-ish passwords from both vaults. Unfortunately, it is possible to continue inputing numerous new logins into 1PW on both devices and be completely ignorant that there is a sync error (and according to you, I've been experiencing this sync error for months. Ideally, you would not force people to upgrade.**ġ) There was no upfront indication that logins were out of sync on the iPhone (iOS 9.3.3) vs Mac (10.8.5). Maybe there is a blog post I missed but life is busy. **You need to educate the user as to why you are so aggressive about upgrading because you may have good security reasons. Of all 3rd party iOS developers, Agilebits is the most draconian at forcing the user into an involuntary upgrade cycle at great cost and inconvenience. I will lose the use of certain apps if I upgrade iOS not to mention lose performance, battery life, and money. As much as your corporate decisions force users to move forward into the next upgrade cycle, other companies' decisions force a user to remain in the past. I acknowledge that doing so puts me at risk of attacks like heartbleed, meltdown, spectre, etc. All of a sudden, after years of reliable syncing, without warning my iOS app is way out of sync with my Mac (which I rarely fire up.its a business travel-only device).įor brevity's sake, take my word that I have good reasons to be using old iOS and MacOS X versions. First, I have encountered the exact same problem as the OP. Please take into account the perspective of the customer. I don't discount that a newer version of 1PW may incorporate some of these suggestions. This is not a rant as much as a constructive heads up that your communication strategy within the app and perhaps your architectural decisions need to be reconsidered.

And want to come to the defense of (OP) and.
