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.
So yes, it's possible to write to the beta, but no, it's not possible to guarantee there will be no last minute breaking changes.
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.
- app with existing location permission in iOS 13 gets precise location.
- when the user prompt appears, it looks like precise location is the default in the UI.
(This is with an app build against iOS 13 SDK -- not sure yet if the iOS 14 SDK changes things.)
I think Apple will likely change this in the future, but right now devs are getting the time they need to adjust.
(As is, this new permission does almost nothing since 99% users will accept the defaults. I think they'll probably require more explicit action on the user's part to get precise location in the future.)
~All of the bugs I've ever seen on a new iOS release are just where they've tightened up some behaviour.
the real things that were dropped since then were 32 bit protected mode apps, and for such you have plenty options for both virtualizing and paravirtualizing.
I can boot basically any other version of Windows under my windows system using Microsoft provided software.
I can even just go boot up older version of Windows on current hardware if needed be, up to a point.
almost everything from eighties to today I am able to run one way another, nothing "stopped" working.
Apple physically removes old software from their delivery platform or signing servers and if you lose your devices it's lost forever
how does it even compare?
Especially considering that only a small percent usually updates to new version of OS in first few days.
Imagine if your app crashes on launch with iOS 14 GM and does not on the latest beta, your business has been materially effected as a result.
Sure it would be nice to have a few days of extra preparation. But the post is obviously a result of pure frustration by developer and is exaggerated.
If you call everyone assholes because of such things then all software industry are assholes.
(From firends/contacts, none of the apps I have to deal with, at least not so far...)
So 15% on the first day, with 1.5 billion active iOS devices. Thats a pretty high number of potential unsattisfied user experience.
I stopped/dropped my iOS dev efforts. I had an app on Apple Store, and eventually pulled it because of the constant updates demanded by Xcode. Yes things were still working, but unless someone is willing to dedicate 'many' days every 3-6-9-12 months to catch-up on new requirements, it's just not worth it. For someone who does dev for a living, it's game on, for others who may want this as a side hustle, it can be overwhelming (keeping up with Apple). I don't blame them, this cat&mouse just didn't work for me. It could as well work just fine for the other part-time/hobby devs.
This just means that every time they change something, the devs have to rebuild, with an unknown amount of time spent. It might be as easy as just changing a couple of lines, or they changed the API so much you have to rethink your code.
And this is for apps that aren't using anything new, it's the old APIs that are changing under them.
I recently pulled it but I had a ios app since 2010, nothing advanced and was only updated every couple of years.
There was only twice I had to do a update because of iOS updates. Once a crashing bug and once to look nice on large screen devices.
I understand the need to progress and develop/create/evolve the programming languages, techniques, environments, it's just not fit for a hobby (in my case)(YMMV).