I thought App developers would be testing against the beta version? I don't really understand the problem. There's public beta's, it's out of beta, and will go to the public tomorrow, apps will continue to work.
You cannot submit you application except using the toolchain that was released today, which is occasionally different enough from the beta tools that your app will no longer work. So now you have a broken app and just hours to fix it, and then somehow App Review is going to get through it while a thousand other people are submitting at the same time you are? No way.
Some apps (Pokemon Go) just crash on launch on 14 without updates.
IOS 14 for developers was available for a long time. Also this is a norm with all SDKs, engines, tools etc - new versions always have new bugs that will be fixed in updates. Especially considering that only a small percent usually updates to new version of OS in first few days.
No one said you HAVE to update your app to iOS14 on day 1. Also, the beta versions have been out for months. If you’re not ready, it’s your fault.
If you’re not out on day 1 and your app has more than a few users, expect bad reviews and bug reports. The beta being out for months doesn’t change the fact that you have something like 15 hours to build and submit your app and hope it gets through review.
The profane language really isn’t necessary. It would be helpful to understand what portion of apps are negatively impacted by the new iOS version. If it’s insignificant, there’s really no strong incentive for Apple to specifically set a launch date with developers. It’s besides the point by the profanity just weakens the argument. Presumably the iOS beta has been out long enough that developers could have pushed out…
Some apps (Pokemon Go) just crash on launch on 14 without updates.
Surely the developers had the 3 month beta period to identify these issues, and ship fixes, right? As far as I understand it, it's possible to ship fixes for a new iOS version before that iOS version actually launches, and indeed that's the idea of the beta period.
The profane language really isn’t necessary. It would be helpful to understand what portion of apps are negatively impacted by the new iOS version. If it’s insignificant, there’s really no strong incentive for Apple to specifically set a launch date with developers. It’s besides the point by the profanity just weakens the argument. Presumably the iOS beta has been out long enough that developers could have pushed out…
> there’s really no strong incentive for Apple to specifically set a launch date with developers
Except that they used to do it a week later every year? And that there is no reason to release it tomorrow, like new hardware that ships with that pre-installed?
> Presumably the iOS beta has been out long enough that developers could have pushed out an update if their app seriously breaks with the update.
You can’t push out an update for the new OS except using the blessed toolchain that Apple released today. That’s what we’re annoyed about, not that the beta period was too short.
Why is this an issue? Apps built with the old SDK will still work on iOS 14, and you can continue to submit apps built with the old SDK for a while. Nothing says your app _has_ to be built with the new SDK on day 1.
Some apps look broken or are actually broken on iOS14.
I’m starting to see a pattern where it’s always the same apps that are broken on each major release. I suspect the developers of those apps are simply incompetent.
Surely the developers had the 3 month beta period to identify these issues, and ship fixes, right? As far as I understand it, it's possible to ship fixes for a new iOS version before that iOS version actually launches, and indeed that's the idea of the beta period.
> it's possible to ship fixes for a new iOS version before that iOS version actually launches No it isn't. Apple doesn't permit code linking against the latest SDK to be submitted until the SDK goes "GM". That happened today.
To expand on this, if your app is "broken" because of changes made that require new OS features in order to "fix" them (such as the new limited permissions for photos, contacts, and location), you were completely unable to issue a new update to fix them until the end of the event. That gives you ≈24 hours to get the new GM, create a build (including setting up your CI system with the new GM, if applicable), make sure no new bugs have been introduced, submit to and get approved by App Review, and launch the update. If you couldn't get all that done in that time, you're probably going to have at least a few negative app reviews from early adopters.