Dropbox Sync Error: Failed to list remote data folder in Dropbox.
I am having a problem syncing via Dropbox. This is on an iPhone 4s, so I am stuck on iOS 9.3.5. I don't think I'm able to upgrade 1Password for iOS either, as when I go to the App Store, I see an "open" button under 1Password (not an "upgrade" button), and 1Password does not show up as apps with updates available in the App store.
The error I am getting is "Failed to list remote data folder in Dropbox. Path: /1Password.agilekeychain/data/default/". Here are some screenshots.
is Dropbox Sync not supported on this version of the app? Will other sync methods work on it?
1Password Version: 6.5.4
Extension Version: Not Provided
OS Version: iOS 9.3.5
Sync Type: Dropbox
Comments
-
Hi @mrengy,
1Password’s Dropbox sync requires 1Password for iOS v6.7 or later:
System requirements for 1Password
If you’d like to sync with Dropbox you’re going to need a newer version. It appears iCloud sync should work, but I can’t say for how long. It may be time for a new device. :)
Ben
0 -
Hi Ben.
So, let me get this straight: unless someone upgrades, your software's main selling feature is broken? WITHOUT notifying your customers? Are you actively trying to turn people away from your product? I've been a loyal customer for many years now and this is not what I expected from your company.
Alex
0 -
@labrinidis: I'm sorry for the confusion. Dropbox isn't and AgileBits product or service; 1Password is. Dropbox changed their APIs, discontinued the old ones, and using the new ones is necessary to connect to them now for a few months:
API v1 is now deprecated (Dropbox)
We're not going to spam our customers (who we don't have email addresses for through the App Store anyway) about Dropbox. If you feel they should have emailed you about changes to their service, you'd have to contact them about that. The only thing we can do is continue updating our software accordingly, which we've done, months before it was mandatory, on both iOS and Android. 1Password for iOS version 6.7 works on iOS 9, which the original poster is running, is years old and no longer supported by Apple, so I'm not sure what you're suggesting, as updating will resolve their issue.
0 -
I want to come to the defense of @mrengy (OP) and @labrinidis . 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. I don't discount that a newer version of 1PW may incorporate some of these suggestions.
Please take into account the perspective of the customer. First, I have encountered the exact same problem as the OP. 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).
For brevity's sake, take my word that I have good reasons to be using old iOS and MacOS X versions. I acknowledge that doing so puts me at risk of attacks like heartbleed, meltdown, spectre, etc. 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 will lose the use of certain apps if I upgrade iOS not to mention lose performance, battery life, and money. 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. **You need to educate the user as to why you are so aggressive about upgrading because you may have good security reasons. Maybe there is a blog post I missed but life is busy. Ideally, you would not force people to upgrade.**
The issues:
1) There was no upfront indication that logins were out of sync on the iPhone (iOS 9.3.3) vs Mac (10.8.5). 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... since the Dropbox API deprecation). That means a headache of reconciling new-ish passwords from both vaults. In other words this is not an issue of restoring or repairing. Its an issue of reconciling.
Even 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. 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. 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. In my case, 29 login items are out of sync (and I don't know which ones without sorting by date). 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. A more visible/front page location for item count would reveal that there was a major disparity. Consider that 1PW for Mac and 1PW for iOS could handshake via Dropbox and confirm that all systems are synchronized as an indicator light to the user. In other words, you need a "check engine" light on 1PW for iOS, Mac, etc. Maybe touching this indicator would show a list of devices and how out of sync they are with each other. Does this already exist in 1PW somewhere?
2) After I encountered head scratching problems...successful login here, unsuccessful there, I then had to manually diagnose the error (I see all of the OP's screens on my iPhone). I'm sure a lot of people got lost at this stage unless they knew to look into Settings>Sync.
3) I googled the error: 'Failed to list remote data folder in Dropbox' and this very thread appears waaaay down the list of search results. In fact, the top post on Google returns a 2 year old thread on discussions.agilebits that offers outdated and incomplete/irrelevant advice. So then I was in dangerous territory of carrying out an obsolete solution that won't work and may cause me data loss (because this is not a matter of restoring from backup, its reconciliation). I suggest using more unique/articulate error strings so that obsolete discussion threads are not dredged up by customers.
4) @brenty directs blame at both Dropbox for changing its API and the customer for not upgrading to newer hardware/iOS. First, Dropbox gave Agilebits a full year of warning that the API v1 would be deprecated...it says so on the link in your comment. Dropbox even had a button to make sure you, Agilebits, acknowledged the change was coming and could wreak havoc if ignored. A solution would have been to roll in Dropbox API v2 into 1PW 6.5.x so that iOS 9 users would never have hit this major bug. You had a year to do this and I doubt there were technical reasons that would prevent API v2 from being implemented in 1PW for iOS v6.5.x.. In your favor, Apple may not let you update older versions of the app because of their own controversial policies.
Alternatively, you certainly could have have warned users many months in advance that their current hardware and software would no longer work reliably without 'spamming' those that had already upgraded. At minimum (and there may be more elegant ways by additionally using iOS Notification Center), Agilebits should have baked in a "Dropbox sync will fail on 7/1/17" dialog box into 1PW and then pushed that out as an update on the AppStore. That dialog box could have been coded to only show where relevant (–e.g., iOS 9) to avoid spamming those that won't be hit by the bug. This dialog box would have been a heads up to me that it was crucial to upgrade my hardware and software by a given deadline instead of the morass I'm in now. Abandoning users and moving ahead was really careless and pour form for a company that has been largely exemplary. If I weren't a developer, I would probably lose my patience and look for a competing PW manager (and to be honest, your new subscription model has me wondering if there are better options).
I understand that you have a very complex product to maintain but your average user will definitely not be aware of that complexity (because 1PW is mostly elegant). Instead, users in our position will see that they paid ~$80 and got left behind. That said, I now see why you opted to create your own cloud sync platform because Dropbox and iCloud are not only potential competitors but also may break at any second. The problem with your 1PW cloud is that I don't want to send my passwords to the very company that both generates and stores them for me locally. It seems like a security risk if there were ever a backdoor in the 1PW. Merely hypothetically, for the sake of an intellectual conversation, uploading my passwords to your 1PW cloud puts the fox in charge of the hen house so customers should always have working cloud and WiFi sync alternatives. The reality is that I believe you guys have made things more secure for me and I'm very grateful but this is an unfortunate headache. Trying to keep all devices in the same window of hardware/software compatibility is getting really onerous.
0 -
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.
We always appreciate feedback from our users, good, bad or just informational, because it gives us a sense of what people's challenges and wishes are. To the degree we get things wrong, we a) feel terrible when it affects customers and b) try to work to correct it as quickly as possible. We feel very fortunate to have such an engaged user base who are willing to take their time to share their experiences with and thoughts about 1Password with us. So, thanks!
For brevity's sake, take my word that I have good reasons to be using old iOS and MacOS X versions.
We believe you, and we trust our savvier, long-time users to make their own decisions when it comes to such matters regarding their own systems. However, such decisions definitely have consequences, and not necessarily ones imposed by us.
I acknowledge that doing so puts me at risk of attacks like heartbleed, meltdown, spectre, etc.
Right. And that's only one example of why, as a security-focused company, we simply cannot recommend users do anything other than update to the latest versions of not only our own software but indeed all OS updates, security patches and updates to the newest version of other software they run as well.
What we won't do is continue troubleshooting legacy versions which have been long out of development, trying to figure out potential issues that might arise from using them with a variety of other unique configurations of older software/versions of OS/related utilities. There just aren't enough developer-hours to make doing that a cost-effective reality if we also want to be focused on serving our customers by making the current iteration of 1Password as good and as secure as it can be while simultaneously looking forward towards defending against emerging threats as well as innovating and incorporating new technologies.
I appreciate your position, and I would respectfully ask that you consider why we have our own. Thanks once again for taking the time to share your thoughts on the matter, and have a great weekend. :)
0 -
so if I've upgraded my iPhone to the latest OS and the 1Password app on my iphone is at version 6.5.2 then should Dropbox work, or will it not? I've been receiving the same "Failed..." error message and ignored it, but now have a new computer so need to get the Dropbox version up to date so I can install it on my new Windows computer using 1Password4.
0 -
@galejl - I'm sorry for the trouble it sounds like you've been having with Dropbox sync. Is 1Password for iOS currently the ONLY copy you have of your 1Password data? And on the new computer, is there a reason you'd choose to go with the legacy 1Password 4 for Windows instead of recently-released, still-in-development 1Password 7 for Windows?
0 -
@galejl: If I'm not mistaken, Dropbox made some changes to their service since that old version was released over a year and a half ago...
Yep. We added support for their new APIs in 6.7, and they shut down the old ones a few months later — almost exactly a year ago. I'm not sure why you wouldn't have updated 1Password, as version 6.9.1 was released last year and supports the same iOS versions, but I'd encourage you to do so. That will allow you to connect to Dropbox there.
0
