Quote:
Originally Posted by Greg Jones
So would it be possible for someone at Omni to comment on what the status is on this? Reading the various posts in multiple threads on the subject, I can't be sure if this is indeed an acknowledged issue that is being worked on, an acknowledged issue that is now fixed and will be incorporated in the next iPhone release, or is considered to not be an OmniFocus issue at all?
|
Some of the posts in the threads are because of a specific issue that will be fixed in the next release. If you're getting a long "optimizing database" screen at the end of the sync, you can safely work around the problem by quitting and restarting the app.
Other posts in the threads are about other issues. Because there are so many factors involved - user behavior, app bugs, network performance, server performance - it can be hard for us to make a determination on the basis of the information in the post.
That is why you see so many "please
email us so we can figure out what's going on" posts. That's the only response that will help that customer without causing more confusion or frustration. (2 customers have similar
symptoms, but the
causes may be different. I can't blame them for both posting in the thread; it matches the symptoms, and they're frustrated.)
Greg, if you frequently see syncs take that long, contact us and we'll help you figure out why. If most of your syncs are fast but this one was slow, the EDGE network or the server being at fault become more likely. We have limited ability to fix problems that exist outside of our code, but we're always happy to investigate.