Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Is this really a problem? So devs can't push a finished app to take advantage of the new features right away, so what. The old apps will work great still and they can take their time and work with the final version in the meantime.
 
Apple in June: iOS 14 will be out this Fall

Devs: Dope

Apple, 7 days before the start of Fall: Hey guys I know it’s been a rough Summer and there’s been some drama in the dev community — but surprise! — you can release your new apps when iOS 14 comes out tomorrow.

Devs: Uh hey not cool, we weren’t ready.

MacRumors users: Awwwww boohoo poor devs.

Surprise, no you can’t submit apps without the right version of XCode which was only released yesterday.
[automerge]1600272051[/automerge]
Is this really a problem? So devs can't push a finished app to take advantage of the new features right away, so what. The old apps will work great still and they can take their time and work with the final version in the meantime.

There’s no guarantee that there won’t be broken APIs which apps are using.
 
I'll just wait to update to iOS14 for a week or so. Let all the latest versions of app funnel into the store. I'm sure my battery life will thank me for not running buggy versions of apps.

14 is better than 13 but after what happened last fall I think waiting for a few days isn't a bad idea. Apps shouldn't drain your battery faster, but they may be buggy in other ways, but it would still be annoying.
 
That’s apples way of saying ... **** you developers, because you re not loud enough defending our App Store Mono (Duo) poly.

apples true Face, emerges more clear recently
 
  • Like
Reactions: tylertc04
Wow. There's a ton of people commenting in this thread who clearly have no idea how software development works. This is a big deal and a bad move on Apple's part. I'd be pissed if I maintained an iOS app.

I bet the same people pissing on the developers in this thread will be the same ones bitching about why some (or maybe most) of their apps won't be ready for iOS 14 today.
 
  • Like
Reactions: aesc80
Apple in June: iOS 14 will be out this Fall

Devs: Dope

Apple, 7 days before the start of Fall: Hey guys I know it’s been a rough Summer and there’s been some drama in the dev community — but surprise! — you can release your new apps when iOS 14 comes out tomorrow.

Devs: Uh hey not cool, we weren’t ready.

MacRumors users: Awwwww boohoo poor devs.
Developing an app takes a lot testing. One day to test isn't enough, unless it's a really small simple app. Also like you said, wasn't supposed to be released until fall, so a lot developers plan their schedules around that date.
 
This is clearly a "Our house, our rules" response from Apple, after the recent events...
 
I'm seeing a common theme with Apple's handling of app's. I know I'll get pounded by die-hard Apple defenders and have simply decided to read and learn more before commenting but Apple is not always on the right side. Numerous cases battling Apple's handling of app's have shown there are absolutely issues with how Apple is handling their service side and it's mostly human related.

Except it doesn't work that way. We always had a week to 10 days to test our apps with the final build.

You also can't be submitting to the store with beta builds of Xcode. We only got the final version of Xcode yesterday and when this happens review times always go way up. So if our app does not work on iOS 14 it could be days to over a week before we can submit a build with iOS 14 that corrects those issues.

The above is absolutely spot on regarding this particular matter and should be pinned at the beginning of this thread if it was possible.
 
So, if you‘re just an everyday user, it sounds like it would be a great idea to wait a week or two before updating to iOS14 so you know your apps will be ready and properly tested. I didn’t intend on jumping on the update right away anyway. Even with beta testing, there still seem to be issues that didn’t get picked up until the software hits the full user environment.
 
How would you know this to make that claim? First its not out for public, and second, the GM came out yesterday. You can make this claim after 24 hours of running a GM build? Unbelievable! 😝

Beta releases have been better so far compared to last year, but they could be problems we haven't faced yet, of course there is no way to know
 
2020 is also full of people who have no idea what they're talking about feeling more confident in their ignorant positions then ever.
Are you telling me your knowledge and expertise has more value than my “feelings” and random, ignorant guesses?

This 2020 is crazy. Experts telling us they know stuff, just because they know stuff. The only way to push back is to do the complete opposite of what they say. That’ll show them we’re just as smart as those so-called “experts”!!1!111!

/s <—Because sometimes people don’t pick up what I put down 🙂
 
Is this really a problem? So devs can't push a finished app to take advantage of the new features right away, so what. The old apps will work great still and they can take their time and work with the final version in the meantime.
Random stuff that worked before can break. There's a good chance it won't, but some apps put a company's reputation on the line, so devs have to be safe.
 
I just updated my phone (was on public beta so assume this is iOS 14 GM) and the weather widget still isn’t fixed. The sun is showing orange instead of yellow. Been this way for numerous betas and I did submit a feedback request. Did iOS 14 drop this week just so Apple could get a week or two of Apple Watch sales in the quarter? Will that even move the needle on financial results? I hope we don’t have another release where people update and the software is full of bugs.

AF916844-23F3-4B06-8642-9CC937D41413.jpeg
 
  • Like
Reactions: nt5672
Well, that is indeed unfortunate for developers and I deeply appreciate their hard workings in this process. However, as a consumer, I have a right to use and enjoy all the features the latest public release of system software (iOS/iPadOS 14 in this case) can offer. And at the same time, developers also have to make sure their applications to be optimized and work as expected under the most recent public release. I sympathize with developers for testing apps in such a short time frame and understand that Apple should take some or major responsibilities in this.

However, as a customer, I am not here to judge whose fault is for causing uncertainties in apps optimization/developing under new system. Actually, It is even not customers’ obligation to be involved between the 2 parties Apple and developers. I only know that customers are rightfully entitled to use apps in latest public release. If the latest system software works well but the apps fail to bring their promises, I will only uninstall those apps but not downgrade the system to “accommodate” developers’ incapability. If possible, I will even look for better and more optimized apps to replace those which perform miserably under the latest system software.

Remember, there are always better alternatives in app market. Only by keeping updating apps with new features and developing in accordance with latest guidelines, developers can remain competitive. Best wishes to you.

As a former app developer, this makes me sad.

As a developer I’ve had to enjoy bug reports from people using betas With no ability to fix them (or wonder if my app is broken in the first place).
 
  • Like
Reactions: uecker87
One of the reasons I’m waiting until at least this weekend to update. Already turned off auto-updates on my phone, iPad, watch, and Apple TV.

I have high hopes for iOS 14, as my past experiences since iOS 7 have been Even versions = smooth and stable, Odd versions = buggy and riddled with issues. We will see how mass rollout goes.
 
  • Like
Reactions: KoolAid-Drink
This is akin to people in a restaurant who complain about their food not being made properly when they have no idea how the hell the kitchen is ran. Sometimes its a horrible kitchen and it's consistent. Othertimes, it's a freak problem (utility outage, staff called out, didn't receive shipment, etc) that people still won't care and just say "Make it right or I'm complaining".

We have the freak event of Apple releasing all GMs and Xcode (huge piece) and have to rebalance everything to make sure our release didn't just break the F out. It's no surprise what the response is in here.
 
You're assuming Beta 1 is the exact same as the GM, and that changes made to the GM didn't cause a bunch of bugs for developers to have to fix in their own apps.

I wasn’t assuming that at all. I was instead assuming that if developers had continued to monitor the betas and their affects on their apps, and corrected problems with their apps following the release of each beta, then that would likely minimize the issues that develop following the release of the gold master (and from what I understand, the gold master contained very few changes as compared to the previous beta).

Am I incorrect in assuming the above?

My point was simply that a developer who had slacked off and waited to make changes because they assumed they’d have a week or two before iOS 14 was released to the public is going to have more difficulty preparing their app for iOS 14 when compared to developers who had been working on their apps following the release of each beta. I don’t know if I feel bad for the former.
 
  • Disagree
Reactions: Yebubbleman
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.