Cannot use contacts after iPhone 3.0 update

[bistro]

When I create a new task, I cannot access contacts at all. This makes the program useless. I deleted it, and installed again, no luck. Any ideas? Thanks
Posted via Mobile Device

[Allibama]

We are aware of this problem and it has been addressed. Since the next version is already awaiting approval from Apple, we probably won't see the fix until version 1.3 - but it has been taken care of. :)

[michael]

Yes, this one "sneaked" up on us...it will be addressed.

[Sulley]

What is this talk of v1.3 of AGiPH? Isn't only v1.01 still pending with Apple? How do we get to v1.3 so quickly?

I had sent this in as a comment in the app itself (about contacts not working under the 3.0 OS). I know Michael said that this will be taken care of, but this removes contact functionality from tasks completely for anyone who has updated to the 3.0 OS.

This issue coming up, after the release of the 3.0 OS, and with Apple taking it's sweet time releasing updates of apps to the App Store, is not a good thing for AGiPH.

When I had downloaded it (about 4-5 after release), the description said that the app had been 3.0 OS tested. That particular line has been removed (I believe it appeared next to the version number on the App Store). Just out of curiousity, was the app really fully tested under 3.0? I would have figured that this would have been caught easily.

It has majorly crippled the app and right now, the only reason I still have it on my iPhone is to be notified of updates as quickly as possible. I have stopped even playing with it.

Alli, what did you mean by v1.3 (I know you work with multiple platforms, so it could have been a typo, but it seemed like a BIG jump in versions unless a lot of new features are coming really soon)? And is there a v1.02 coming QUICKLY to be submitted to Apple to resolve this issue and possibly some of the other problems as well (e.g. clipping of names in contacts is a big one I can think of) that I don't think was addressed in v1.01, unless I missed it on the list?

Adriano did say in his sticky note about calendaring that those features would be coming in a matter of weeks (as opposed to months), but I am starting to wonder if that is even achievable. I was hoping it was, but with Apple running in first gear, which isn't iambic's fault at all, it's frustrating to know that we've got a long road to tow.

I'd appreciate some feedback from Adriano and Michael on this...

[michael]

Sorry for the confusion. There is no 1.3. 1.01 has been submitted to the App Store and 1.02 is under development. This fix will be part of the 1.02 update. AGiPH was tested for 3.0 for stability and very basic things like crashes, but because of poor timing, as far as when Apple released the 3.0 update (officially) and us submitting, we couldn't get it in the 1.01 update.

Yes the time from submission to release by Apple is a bit frustrating, but we are at their mercy in that department.

[Allibama]

Sorry, got my numbers crossed there. Nonetheless, you know you will always be fighting a version behind with the way apple holds things for approval.

[Sulley]

Thanks for the clarification Michael and Alli. I knew v1.3 had to be a typo (or a case of platform confusion). I definitely know that you're at Apple's mercy once an app is submitted for posting to the App Store. No blame was intended at all, in fact I think I made it clear that it wasn't your fault in any way.

Well, right now, in Apple's defense, they have an onslaught of new apps and updated apps that have been submitted for all kinds of reasons associated with the release of the 3.0 OS. They are just inundated with apps wanting posting in the App Store. They are also dealing with the issues of what they will and won't approve given the implementation of Parental Controls in the 3.0 release. But, that shouldn't affect apps that are clearly not in that kind of situation, like AGiPH.

Typical version upgrade posting dates run under a week (for bug fixes, minor feature additions, etc.), on average, but if Apple is feeling slow, anything can happen (taking up to months, in controversial cases in particular). Major version upgrades can take a little longer for Apple to dig through. I've heard this directly from a number of developers from their experiences.

AGiPH v1.0 got posted a few weeks before the release of the 3.0 OS, so it was just unlucky timing now that you need to get maintenance upgrades passed through quickly. It's just a shame.

Is v1.02 going to be the version which implements calendaring? I'm curious to know if it will be another maintenance/minor update release (with a shorter turn-around time) or a larger upgrade, with calendaring, that is going to take at least a few weeks to get built. Is there any way that we could be privy to what you're planning for v1.02 so that we can comment on what is really important to us and give feedback on your plans?

Until v1.01 is released, we can't make any comments on what we think needs to be in v1.02, but once it is, I'd like to be able to throw out a list of things that would be important to me. If v1.02 is only the calendaring addition, plus putting out fires (e.g. the contact bug with the 3.0 OS), then that feedback is not going to be necessary.

Any feedback on these questions?