Please cut the guys at OmniGroup a bit of slack. This is definitely an annoying and embarrassing issue, but we’re all only human - mistakes happen. Once the issue was discovered, they were very fast to respond – on a Friday night, no less. They had a fix released in a matter of hours.
The only reason we’re still talking about this issue and the that the outage wasn’t over shortly after it began is the App store review process. The Omnigroup has done all they could, as quickly as they could, to address this issue; now, we’re just waiting on Apple.
Is there anyone from OmniGroup to us with this situation, at least expressed. Personally for OmniFocus for iPad 2 (yet) important to me. I think that as paying customers deserve. @OmniGroup, Thanks for the response.
I’m sure OmniFocus support is doing all they can right now. Imagine how many thousands of emails they must have streaming in about this issue as we speak. Even if they’ve called their entire support group in to work the week, which I’m sure they have, there’s only so much you can deal with at once.
High standards of quality and support are what Omni is selling. OF is complicated, inflexible, and slow to load and sync relative to competitors. However, it is feature-rich and has had a reliable sync. Probably this is single very unfortunate oversight, but it does involve a key asset of Omnigroup: user trust.
We’ll see how it will look on Monday. I need to plan your time. If it does not work with OmniFocus, it will go with something else.
BTW: From your replies I have the impression that for the customer as I can myself. I respect your opinion, but do not agree with him.
What should have been on OmniGroup’s company iPad OF2
—Delete beta test build from App Store
—Upload the real deal iPad OF2 to avoid having egg on our face
Wow- This is rough after spending $30 and moving my system over to this just this week. Charging more should mean better service… How can I find out when it is back up?
@daryl: So what? All they (can) do is sending out the pre-defined, standardized message (see above). No big deal for the support team. No weekend work call-in neccessary.
Yes same problem for me.
Reading the blog, it appears that the fix was small in nature. But why was it over looked in the first place?
For a while after Steve Jobs died, everything Apple continued º long the lines of “it just works” this appears to be no longer the case. Are we so reliant upon technology that we no longer have to think about what one does or is responsible for?
That technology will tell us when we have done something wrong or not done it at all. Technology is not that good, that it can save us from ourselves. Or in the case of the OF developers save them from their complacency!
Sadly, I fear it will, for quite a while until fixed.
But hey, you are amongst the “good guys” in app development, and as stupid and embarrassing as this is, I’m sure the goodwill you have built in the Mac and iOS community will buy you a bit of slack. Good luck with getting Apple to react quickly!
Omnifocus really dropped xt he ball on this one. Submitting app updates is a repeat process. If they kept a todo list in Omnifocus on the steps necessary to release a major update this would not have happened!
On the other hand if you use there sync solution you will never miss a todo because you can easily continue work on iPhone or Mac
In case folks haven’t been following the updates on our blog and in the pinned timeline thread, the fixed 2.0.1 release was approved about 11 hours ago and is now available as a free update:
Again, our sincere apologies for the error!
(I’m closing this thread so that this resolution is easy for folks reading the thread to find, but I don’t mean to discourage further discussion. Please feel free to reply to this post in a new thread.)
