App Store Submissions Now Being Reviewed for iPhone OS 3.0 Compatibility

[shaun.andrews]

It's actually very easy:

1) Test your app in 3.0
2) Log your bugs
3) report OS bugs to Apple
4) Wait for the 3.0 version that fixes the bugs
5) Retest your app.
6) repeat as needed.

And in the mean time, while I'm waiting for Apple to fix *their* bugs, does my app sit in limbo waiting to be accepted—all the while I lose potential sales because my app doesn't work on beta software? I understand the need/want to make sure apps work with the new OS, but requiring apps to work with buggy software doesn't help anyone.

 

[notjustjay]

So what do you think will happen if developers don't update their apps to work with 3.0 but customers have paid for them? How will they handle refunds of that magnitude?

I've bought many Classic apps that never made the transition to OS X, apps that worked in Panther that stopped working in Tiger or Leopard, and apps that were built for PPC that never made it to Intel. I'm not expecting refunds on any of those.

 

[TuffLuffJimmy]

And in the mean time, while I'm waiting for Apple to fix *their* bugs, does my app sit in limbo waiting to be accepted—all the while I lose potential sales because my app doesn't work on beta software? I understand the need/want to make sure apps work with the new OS, but requiring apps to work with buggy software doesn't help anyone.

You will probably have the Gold Master firmware before the public, so you'll have time to bug fix and get your app in the store before 3.0

 

[AtlasBoy]

And in the mean time, while I'm waiting for Apple to fix *their* bugs, does my app sit in limbo waiting to be accepted—all the while I lose potential sales because my app doesn't work on beta software? I understand the need/want to make sure apps work with the new OS, but requiring apps to work with buggy software doesn't help anyone.

The email says "Beginning today, all submissions to the App Store will be reviewed on the latest beta of iPhone OS 3.0. " So the question becomes have you submitted your app before today. If so, it seems there is no requirement for 3.0 compatibility. It you have not submitted it, you could read the compatibility notes that came with the release and *most likely* get your app to work with 3.0. in short order. If not, your apps not ready yet and submission is a moot point IMO.

 

[Sehnsucht]

Hell yeah...

All right! Can't wait for my apps to stop crashing! Most apps are fine, but 3.0 definitely made some of them go batsh*t. BeejiveIM, for example, has a nasty habit of displaying a blank black screen when I try to view my buddy list:

I also had to disable Beejive's landscape mode because every time I rotate my iPod touch to use the landscape keyboard, Beejive freezes solid. (Beejive had always run smooth and stable on 2.2.1). And in another extreme case, Dungeon Defense doesn't run at all. Repeat, does not run. It will display a splash screen for a few seconds and then poof! Back to the home screen.

3.0 builds 3 through 5 have been acceptably stable in terms of the OS itself. No funky graphics issues with Cover Flow like I noticed in 2.2.1 and before.

 

[admanimal]

This is exactly my current issue. I only have ONE iPhone. I've only developed ONE app. I don't want to install 3.0 beta, but I guess I am going to have to. When the new iPhone is released i'll be keeping this phone for development/backup only... but until then i only have 1.

Can your app run entirely on the simulator? While maybe not 100% foolproof, running your app on the 3.0 simulator if possible should be enough to check for most bugs if its your only option.

 

[msephton]

Which email address was this notification sent to? I'm a registered developer and am yet to get the email.

An app I submitted on Friday was rejected, not sure quite why just yet.

And finally, what's the recommended upgrade path for the SDK that will still let me submit? Install 3.0 SDK over 2.2.1 SDk and build as 2.2.1? Or a side-by-side installation?

Thanks,
matt

edit: just called Apple Developer Connection and they said not all developers were sent this email. Some may receive it later. Not sure what the criteria is.

 

[PabloGS]

Why would schools be any different than other developers? Why wouldn't Apple allow them to join the iPhone Dev Program?

I read some place that schools and unis aren't in the 3.0 beta program yet!

 

[DELLsFan]

3.0 will still be released during WWDC, along with preview of final version of Snow Leopard.

I think WWDC this year will focus on two things: First half toward iPhone OS 3.0, and second half toward Snow Leopard (released during Autumn)'

One more Thing: First Blu-Ray Macs, the all new Mac Pro.

Ohhh ... don't tease me ... I'm just about ready to buy a Pro. Now I'll probably torture myself for another month or so!

 

[W1LLk]

So can we expect 3.0 sooner than anticipated?
I hope not. I want a near bugless release.

I really don't think WWDC is sooner than anticipated, I think that's more like the earliest anticipated...

Ohhh ... don't tease me ... I'm just about ready to buy a Pro. Now I'll probably torture myself for another month or so!

I suggest breathing into a brown paper bag. This is always the hardest time to hold out on something you want, but you must. For an Apple fan in the know, it makes no sense to purchase something within a month or so of WWDC, unless you like making your hardware absolutely obsolete within 1 month of ownership...

 

[odedia]

This seems a bit demanding to me. What is wrong with the current framework, where apps list system requirements? I would think 3.0 apps could be listed as such without forcing all developers to either ensure 3.0 compatibility or have their app removed.

Let's hope Apple doesn't start requiring all applications for the Mac to be Snow-Leopard compatible once that comes out! (I don't really think they would.)

iPhone OS is a free update, Snow Leopard is not.

So I think it's a fair demand on their part.

 

[ert3]

So i guess they aren't going to be trying to make the OS work with 2.0 apps after all what a big surprise.

 

[johnnyjibbs]

I haven't yet received that email. But I suppose it's about time to think about getting a device to put 3.0 on, then work on an app that uses the features for a first day launch...

 

[MDiddy]

As an developer, iPhone OS 3.0 has MASSIVE architecture changes.

Therefore, many of the apps right now in the app store has major incompatibilities with iPhone OS 3.0. (even with many beta changes)

The changes are easy to make. Just change few lines of code, and it should work.

I think Apple is all about making sure the apps work in the consumer end.

Demanding? Yes! Thinking about consumers? ABSOLUTELY!

Think about developers and make the 3.0 SDK free already then.

 

[Mal]

Think about developers and make the 3.0 SDK free already then.

Umm, isn't the SDK free already? I mean, yeah, you have to pay for the certificate so you can put apps up on the store, and since 3.0 is beta still it makes sense for them to allow access for those developers even if they don't allow it for everyone, but no one is paying for access to the 3.0 beta software.

jW

 

[BJWanlund]

This, along with the fact that Sling Media is showing up when one searches for "slingplayer" in iTunes desktop, is proof positive to me that iPhone OS 3.0 is coming sooner than we all anticipated... like within the next week.

BJ

 

[admanimal]

is proof positive to me that iPhone OS 3.0 is coming sooner than we all anticipated... like within the next week.

BJ

There is zero chance that is going to happen...not to mention that the email stated that millions of customers would move to iPhone OS 3.0 this summer.

So i guess they aren't going to be trying to make the OS work with 2.0 apps after all what a big surprise.

I would guess tthat at least 90% of existing 2.0 apps that were properly written to begin with will work without modification on iPhone OS 3.0, which was obviously Apple's intention.

 

[BJWanlund]

There is zero chance that is going to happen...not to mention that the email stated that millions of customers would move to iPhone OS 3.0 this summer.

So why wouldn't Apple destroy everyone's expectations and put out iPhone OS 3.0 this month? Besides, the fact that all iPhone software is going to require 3.0 compatibility from this point forward suggests that Apple has enough confidence in iPhone OS 3.0 being as largely bug-free as possible that they're ready to roll it out almost a month early.

And with some applications that may require the APIs in iPhone 3.0 (Slingplayer iPhone) being "leaked" onto iTunes (and Leaf Trombone: World Stage being ALREADY UP ON THE APP STORE), I feel that the chances are slightly greater than zero.

If you want to hit me over the head with your evidence about "this summer", do your research. It might not be near the summer solstice when this is released, but I am thinking that "this summer" could start within the next several weeks and last until early August. Just saying.

BJ

 

[admanimal]

So why wouldn't Apple destroy everyone's expectations and put out iPhone OS 3.0 this month? Besides, the fact that all iPhone software is going to require 3.0 compatibility from this point forward suggests that Apple has enough confidence in iPhone OS 3.0 being as largely bug-free as possible that they're ready to roll it out almost a month early.

And with some applications that may require the APIs in iPhone 3.0 (Slingplayer iPhone) being "leaked" onto iTunes (and Leaf Trombone: World Stage being ALREADY UP ON THE APP STORE), I feel that the chances are slightly greater than zero.

If you want to hit me over the head with your evidence about "this summer", do your research. It might not be near the summer solstice when this is released, but I am thinking that "this summer" could start within the next several weeks and last until early August. Just saying.

BJ

I guess we'll just wait and see...

How could Leaf Trombone require 3.0 APIs if people are already downloading it and using it without 3.0? It can't even be built to support 3.0-only features because in order to do so, it would have to be compiled against the 3.0 SDK, which again would prevent it from working on any device without OS 3.0 already on it.

 

[zey]

The changes are easy to make. Just change few lines of code, and it should work. [...] Demanding? Yes! Thinking about consumers? ABSOLUTELY!

I do feel a bit sorry for the developers though. It must give them ulcers waiting out the days or weeks for the Completely At Random® approvals process to finally yay or nay their app.