It's been sent to Apple for their 'pre-release checks', so we're just waiting for Apple to accept and publish it in the App Store.
- Strike that, I've just been informed by Marketing that they've decided to hold off on release of the iRFR until Eos/Ion 1.5 is released, as it's not supported in Eos/Ion 1.4.5.
Latest update from Anne is that we're now hoping for end-of-May for both releases. A few annoying bugs were discovered recently that we'd really like to squash.
[edited by: Richard at 4:39 AM (GMT -6) on Mon, May 4 2009]
This really sucks for the Congo users that could be using it now! If the app is really ready and has been sent to Apple for approval, why can't they release it with a warning that it won't be available for the Eos until 1.5? Then the Congo users can "beta test" it before the Eos/Ion users have it working for them. It doesn't seem fair to make us wait just because the Eos guys have to wait. Which brings up the question, if it was ready for the Eos now and it wouldn't work for Congo until v6 (rumored to be out this summer), would they hold off on the release until Congo had their update?
[edited by: lidgett at 7:52 AM (GMT -6) on Fri, May 1 2009]
This really sucks for the Congo users that could be using it now! If the app is really ready and has been sent to Apple for approval, why can't they release it with a warning that it won't be available for the Eos until 1.5? Then the Congo users can "beta test" it before the Eos/Ion users have it working for them. It doesn't seem fair to make us wait just because the Eos guys have to wait. Which brings up the question, if it was ready for the Eos now and it wouldn't work for Congo until v6 (rumored to be out this summer), would they hold off on the release until Congo had their update?
[edited by: lidgett at 7:52 AM (GMT -6) on Fri, May 1 2009]
I'll add my vote for that sucking, if it's ready to go for Congo users, waiting for "marketing reasons" after dangling it infront of us and announcing it as "soon" is really sucky.
