I’ve done a lot of work rewriting the Dropbox code in SwiftoDo. At this point, any error messages it generates are a now a little less well written—they are more generic—but they will appear more quickly, with greater consistency, and will reappear (as you would expect) each time Dropbox is accessed until the problem is fixed. Plus, the new error messages will provide a little more information about what went wrong than they did before. I hope it’s the right tradeoff.