> the final public release of iOS 14 ships tomorrow, which came as quite a shock to all third-party developers. Really? This is the way they have done the releases for about 10 years now.
Nope, they ship a GM a week in advance.
Why is Apple acting like an asshole?
61–70 of 515 posts
Re: Why is Apple acting like an asshole?
#62This article is missing the best part, that the new Xcode you have to use to build your app was released today at 11 AM, with a build number of ‘208. It was a really strange build in that it was missing components to build for Apple silicon: for that you need to use the old beta, which Apple has kept up on their website so you can juggle both. But that’s not all! Soon afterwards they changed the website saying the ne…
> iOS developer hates with a passion and gives no useful information That's typical Apple, they are allergic to technical info and error display, when things are not working, there's no way to know why.
All in the name of UI cleanliness and simplicity. Like how there's no way to manually trigger the firmware update for the AirPods. You just have to keep them plugged in next to your iPhone and ... wait ... until some magic pixie in Apple's cloud decides it's time to push the update to you.
Steve Jobs used to say it over and over again when criticized by angry developers[1] that their main focus will always be users instead of developers and that the latter will just have to suck it up if they want to get a piece of the lucrative Apple user base pie.
In comedic contrast, here's a sweaty Steve Balmer shouting "Developers!" for half a minute.[2]
Ah, the early 2000's, with Apple and Microsoft battling it out, what a time to be alive.
Re: Why is Apple acting like an asshole?
#63Earlier quoted context omitted.
Well you can always ship updates with the old iOS 13 SDK toolchain (Xcode 11) the entire time. You could have tested on the iOS 14 betas, and if you found a crash, you could try to implement a workaround and resubmit in the weeks and months leading up to today. Sometimes your crash is because of bad assumptions in your code, or sometimes your crash is due to real Apple bugs creeping into the iOS APIs. Not saying it's…
That is correct. But I know for many apps building for iOS 14 is a requirement or bad things will happen™.
Care to elaborate? Did Apple break backwards compatibility with apps built on the iOS 13 SDK with no way to work around it? Seems hard to believe that everyone upgrading to iOS 14 will end up with no functional third party apps today?
Re: Why is Apple acting like an asshole?
#64Earlier quoted context omitted.
Web is great for a lot of things. But not games, especially if you want efficiency.
Or things like real time audio processing, AR or on device ML. Anything thats not a JSON viewer or CRUD app basically.
I think that is a very pessimistic view of what you actually can achieve in a browser! With web assembly a lot of those things actually are very possible today.
Re: Why is Apple acting like an asshole?
#65Wait, what? Did Apple announce that GM is released to public beta, or did they announce that they are actually pushing out iOS 14 to over 1B devices as of tomorrow? Because the two are very different. If it’s the former, I agree with the author that it’s a complete disaster for a lot of development teams. There is really no sane reason to do something like this, so I just can’t imagine it’s true — it’s not like the OS update has to be pushed out ASAP because some magical new device or service requires it.
Re: Why is Apple acting like an asshole?
#66Earlier quoted context omitted.
> iOS developer hates with a passion and gives no useful information That's typical Apple, they are allergic to technical info and error display, when things are not working, there's no way to know why.
All in the name of UI cleanliness and simplicity . Like how there's no way to manually trigger the firmware update for the AirPods. You just have to keep them plugged in next to your iPhone and ... wait ... until some magic pixie in Apple's cloud decides it's time to push the update to you. Steve Jobs used to say it over and over again when criticized by angry developers[1] that their main focus will always be users…
Yeah, I guess some people decided that technical errors helping you to find what is going on are "ugly".
Re: Why is Apple acting like an asshole?
#67Earlier quoted context omitted.
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.
Or they're always on the bleeding edge using the latest features.
Re: Why is Apple acting like an asshole?
#68Wait, what? Did Apple announce that GM is released to public beta, or did they announce that they are actually pushing out iOS 14 to over 1B devices as of tomorrow? Because the two are very different. If it’s the former, I agree with the author that it’s a complete disaster for a lot of development teams. There is really no sane reason to do something like this, so I just can’t imagine it’s true — it’s not like the O…
Latter: iOS 14 is going out to 2 billion devices tomorrow, probably 10 AM.
Re: Why is Apple acting like an asshole?
#69I 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.
deleted
Re: Why is Apple acting like an asshole?
#70I've been using the betas, and haven't had any problems with the apps. What patches are required for apps to work on iOS 14?
If you use some sort of thing that the new privacy things will block you need to update to account for the new behavior. If you have new features you want users to have you need to build with the new SDK. If you have fixes for your app being broken (either because of you or Apple’s bugs) you need to fix them.
> If you use some sort of thing that the new privacy things will block you need to update to account for the new behavior.
I am not shedding a tear for the producers of the apps that used privacy invading code all the time, and didn't stop since iOS betas exist, waiting instead for "official iOS 14" to "do something" -- which is probably forcing the user to agree or not use the app.
I hope I'm wrong, and to accept that I'd need a specific example.