51–60 of 515 posts
I'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?
Earlier quoted context omitted.
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.
Earlier quoted context omitted.
Some apps (Pokemon Go) just crash on launch on 14 without updates.
This isn't an sdk issue, it's a purposeful decision by Niantic to not support beta OSes to avoid potential exploits. Fwiw it finally works now with the 14 GM that went out :)
Earlier quoted context omitted.
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.
Uptake is very rapid, and new bugs can show up between a beta and a GM release of iOS. It's not enough baking time to test against a GM version of iOS and successfully submit an update to the app store that is accepted and reviewed that is the issue here. 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.
Really? This is the way they have done the releases for about 10 years now.
I fail to see the point, as far as I know Apple has been vocal about iOS since WWDC and typically releases the OS relatively quick after events. The beta's been out and available for every iOS developer for months in order to prepare for this. There's enough to rib on Apple on, but this really doesn't seem like one?
Apple has always given one week to use the golden master tools and build to run final tests on and submit your applications so they can be out before a million people try to install it on iOS 14. If your iOS distribution person is out on a camping trip for a couple days, you’re not hitting the deadline anymore. If you live in certain parts of the world where you wake up 7 hours after the event and Xcode takes fifteen…
Earlier quoted context omitted.
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.
I have applications and games from the 90s that still work in Windows 10. The idea that developers have have to constantly push updates is unproductive in my opinion.
This 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…
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.
I fail to see the point, as far as I know Apple has been vocal about iOS since WWDC and typically releases the OS relatively quick after events. The beta's been out and available for every iOS developer for months in order to prepare for this. There's enough to rib on Apple on, but this really doesn't seem like one?
The App Store submission process is tightly integrated with the Xcode version used to build the app, if you want to be ready before users upgrade the App Store needs to be updated at least a few days before users automatically get the update. The App Store being updated to allow builds from the new version of Xcode is the most important issue. That only happened after 2pm ET on the 15th, and I’ve seen report their had been some delay (thankfully I only had to verify existing builds and didn’t need to submit a new build today). This means even if you had your build completely done based on pre Golden Master beta, and can either quickly reverify it or are comfortable just throwing it out there, you could only actually submit it today. Review times even without back and forth over policy points can take multiple days. Things will be worse for users over the next couple days.
iOS betas are frequently quite noisy and variable, if you test against an early beta you will need to retest against the actual GM with potential backwards compatible breaks each time. If you are either unlikely to have bugs or have enough capacity to spike doing a lot of work within a week you have the option of only doing the expensive thorough verification work against a single release.
There are still many reasons why real device testing with the production IAP environment are necessary. This is mostly a failure on Apple’s part to ever update their test environment’s capabilities and achieve parity with production. Doing this early requires you to be able to afford and have extra hardware of spend extra time having to upgrade and downgrade OS versions in order to verify the new version and continue to support live production hot fixes and support. A week between GM and GA is in the Goldilocks zone for developers, so that if they’re not doing a huge release to correspond with the iOS version they can upgrade test devices once, do one chunk of testing and fixing issues, and have their own build which will happily support both the old and new OS reviewer and live before users actually get the new OS.