[Ken Case]

We're still exploring this: the API documentation seems to indicate that we should be able to make syncing work in the background, and we thought that what we'd already done (setting up a task completion block for our syncing) would in fact allow it to proceed in the background.

But when we tested our code and watched the server logs, we found that when OmniFocus moved to the background we would stop sending HTTP requests (despite our active task completion block)—so at the last minute I pulled the release note which said that our background-awareness added support for syncing after leaving the app since that didn't actually seem to be working.

At that time we didn't have time to look into it further (since we were busy trying to finish OmniFocus for iPad), but now that we have a bit more flexibility in our schedule we'll be looking at this again.

P.S. — Note that iOS only allows specific background operations; it doesn't have a notion of syncing in the background in general. We think we should be able to schedule a sync to happen right as you quit the app, but we won't be able to wake up OmniFocus every few hours to sync any changes that happened while you were out of the app.