I had wondered if they were just a bot, really. Spelling mistakes aside, you are correct about how they comment within minutes of a new article. But then they could also just be a person who wants some internet karma and posts whatever they want. Whichever it is I only roll my eyes when I see them post, and I’m not one to put personal anything into a conversation on the internet...unless you really piss me off (and that is rare) or you attack me directly lol.
Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Developers Frustrated at Apple for Just One Day's Notice to Submit Apps Ahead of iOS 14 Release Today
- Thread starter MacRumors
- Start date
- Sort by reaction score
I had wondered if they were just a bot, really. Spelling mistakes aside, you are correct about how they comment within minutes of a new article. But then they could also just be a person who wants some internet karma and posts whatever they want. Whichever it is I only roll my eyes when I see them post, and I’m not one to put personal anything into a conversation on the internet...unless you really piss me off (and that is rare) or you attack me directly lol.
They've known since June. On top of that, we've had September releases how many times now?
Update: The answer is 10.
If your app is broken for iOS 14 you had no chance to fix it. So you submit a update to your broken iOS 14 app which you were only able to do starting late yesterday and if it takes several days for app approval you have a broken app on the store with millions of people updating to iOS 14.
In years developers have more of an opportunity to correct this with the week to 10 days we always had in-between getting the GM and it being public.
Hi Danny (we know each other from a different forum)...so pretty much, app users should just be realistic and understand that all developers faced the same issues here? In other words, just don't update to iOS 14 for a week or two?
Edit: Also, I've been running iOS 14 since B1 and I've really had no app issues (but I do understand that they exist).
Based on this news story and thread alone can someone explain the whole Beta process? I don't get how you get 8 various betas that span over 2 months (From WWDC to today) and developers are complaining they only had a day with IOS 14. No they didn't only have a day. They had 2 months. And when they do update the apps the notes are basically going to be "Compatible for IOS 14" or "Bug Fixes". I would be more sympathetic if developers actually used the betas as they were designed and not be lazy in terms of update descriptions. You guys had 2+ months.
Some of these “devs” are just people who want attention and likes on Twitser. The apps they made have been compatible for weeks. Some don’t even know that Xcode was released yesterday.
The need for attention on unsocial media turns people into morons.
The need for attention on unsocial media turns people into morons.
you really don’t understand how it works do you? most developers ARE ready with new app versions but you can NOT submit an app for the iOS 14 GM build without processing it using the GM build of xCode which came out yesterday afternoon! An Xcode build that had issues that for many made it unable to work until last night! There was literally no way for a developer to even submit an app that used iOS 14 features until 12-18 hours before the release of iOS 14! That’s assuming they don’t bother to even test their app against the final GM that also only came out yesterday to see if last minute bugs creep up etc.! And that’s assuming the thousands and thousands of apps have even a chance of being approved by Apple in the hours left to make the release!
the bottom line is today ios14 will come out and apps won’t work properly and won’t take advantage of iOS 14 features not because of developers but because of the sheer lack of caring on the part of Apple. Had apple released the GM last week OR delayed the release of iOS 14 and Apple Watch until a week from now this wouldn’t be a problem but now the world, like you, will blame developers when it’s the folks in Cupertino that are to blame.
Yeah I recognize the username lol. I’m more addressing the people complaining saying “developers had the entire summer to update their apps, what’s the excuse” without really understanding how the whole process works.
1. Apps which have the new iOS 14 features (widgets) would like to launch with iOS 14 to get the day 1 exposure.
2. If an app works fine in iOS 13 but crashes in iOS14 they want the app update to be ready so their app won't get 1 star reviews due to the crash.
Apple just allowed developers to submit apps yesterday with iOS 14 support. Not all apps submitted yesterday will get approved in time. Knowing Apple they might reject an app because it used a wrong color. For those cases there would be no time to submit for re-review.
Developers and the app review teams probably worked alot of overtime last night. If an app doesn't function properly after you update to iOS 14 please give them a little slack.
Unless you’re an app developer (which I’m not) I’m thinking there’s a crap load of behind the scenes stuff that would cause the stir among developers. Obviously it’s not as easy otherwise you would be making apps too.
so now when the apps crash don’t complain “cause they had a whole summer” of a bug filled unfinished IOS
so now when the apps crash don’t complain “cause they had a whole summer” of a bug filled unfinished IOS
Lots of armchair developers in the thread. I am not a developer. I apologize for nearly posting that they had all summer, seemed like plenty of time.
Fellow Non-developers: please take the time to even just scroll through the comments from actual developers. You’ll see that Apple just barely released required final tools to submit their app, meaning giving literally 24 hours. You’ll also see developers that say the latest beta to grand master broke multiple of their apps, again leaving them with 24 hours to fix and submit. There are many more examples that show it’s not a case of laziness or being unprepared.
I always look forward to grabbing the new iOS version on day one. But thinking back, we always knew what that date was at least a week in advance, because for a week I’d be like a kid waiting for Christmas. Very odd that we had a keynote and it’s out the next day with no heads up! Feels unprecedented. Maybe Apple was unsure of release date themselves and wanted to just go for it. I don’t know, it’s very 2020 I guess.
Fellow Non-developers: please take the time to even just scroll through the comments from actual developers. You’ll see that Apple just barely released required final tools to submit their app, meaning giving literally 24 hours. You’ll also see developers that say the latest beta to grand master broke multiple of their apps, again leaving them with 24 hours to fix and submit. There are many more examples that show it’s not a case of laziness or being unprepared.
I always look forward to grabbing the new iOS version on day one. But thinking back, we always knew what that date was at least a week in advance, because for a week I’d be like a kid waiting for Christmas. Very odd that we had a keynote and it’s out the next day with no heads up! Feels unprecedented. Maybe Apple was unsure of release date themselves and wanted to just go for it. I don’t know, it’s very 2020 I guess.
Reviews are pretty fast, but since "everyone" is updating this week you can expect some delays.
And you also have to download the latest Xcode, build the project, do a quick test with the GM and then submit. You can do it in one day, but if you find a new bug with the GM you may miss day one.
If the current version of your app built for 13 is still ok, there is no rush unless you want your users to have the new features (like Widget) on day one. That's my case, I don't have new features to submit immediately so I'm not affected by the delay, but many others are
Well, if I am understanding this correctly...they did have months to get their apps ready to be submitted for updating, no? The obstacle was actually submitting it to Apple for the update. So theoretically, if developers had been modifying their apps to prepare it for iOS 14 since the early beta stages, then yesterday, when the ability to submit their app to Apple for iOS 14 was actually made available, they would have been able to promptly submit it to Apple; is that correct or am I missing something?
Ah was curious about the widgets, but since developers didn't get the needed time to submit apps by Apple I'll hold off till next week or later.
Older apps won't stop working on iOS 13, but may not work on iOS 14. There's always changes and upgrades you have to make to make the apps compatible with multiple versions of iOS.
Usually the most reliable testing you can do is between the GM build (which is the beta that usually matches the release) and the release. You usually get a week to two weeks to test on the GM to make sure any changes between the last beta and the GM are accounted for and fixed if needed.
Apple gave developers 1 day, so any changes they made in the iOS 14 beta 8 and the GM couldn't be tested against. We have two apps at work that broke between beta 8 and the GM (I'm not on that team so I can't answer what exactly broke I just know they broke). That team had one day to find the bugs, fix the bugs, and do a full regression test then try and submit their app to Apple who will take time to approve it.
Then there's the issue with only being able to submit apps for approval using the GM build. Developers could only submit since yesterday afternoon so many won't have bug fixes for iOS 14 in and if early adopters use an app that iOS 14 breaks, they'll trash that app in the App Store reviews when the developer had no way of getting their fix in due to Apple dropping the GM the day before release. The developer loses in this instance and so does the user who doesn't have a working app on the store until their update goes through.
There's zero wiggle room, and here's why: All it takes is for the early iOS 14 adopters to see a feature doesn't work and destroy your app in the App Store.
I really dont like people taking an anti-developer, pro-Apple knee jerk reaction here.
You guys do realize iOS wouldn't be what it is, without developers -- right?
I remember the iPhone days before there even was an App Store. It was cool, for its time, but prohibitively narrow in functionality.
in my view, it was not enough notice.
You guys do realize iOS wouldn't be what it is, without developers -- right?
I remember the iPhone days before there even was an App Store. It was cool, for its time, but prohibitively narrow in functionality.
in my view, it was not enough notice.
Because that's how lineups/ques work. Like, if a million people need to submit something at the same time, creating a backlog of 10 days - obviously there are many that will be at the front of that line and be done within one day, or even one hour.
For ****s sake, this has been explained multiple times in this thread.
DEVELOPERS COULD NOT SUBMIT iOS 14 APPS UNTIL LAST NIGHT
If their apps were not working in iOS 14, they could have fixed it over the past few months, but they could not submit it until last night. The review process takes some time, and their update may not be available for download for several days. In the meantime, anyone who upgrades to iOS 14 tomorrow will not be able to use that app. This reflects poorly on the developer and will piss off users, especially those who paid for it.
Lastly, developers have had no time to test on the GM release. Rule number one of software development is you do not release code that has only been tested on beta operating systems. EVER. Developers will need to retest everything on GM and have had less than 24 hours to do so.
I think people under-estimate the importance financially and in terms of morale of a launch window, particularly to small independent developers. Getting written up by tech blogs or featured by Apple as part of the launch of an iOS version is make-or-break for many apps people make as passion projects, projects that don't start out generating enough income to be full-time jobs. The momentum from a launch day feature somewhere has been the push many needed to start building those passion projects for a living — or to putting serious time and emotional energy into making them happen. A lot of community favorite apps started this way — Drafts, Day One, Apollo, Instapaper, etc. So it's very personal to a lot of us in that community of smaller developers trying to grow our work.
When you have less than 24 hours after receiving a version of the software required to submit your app that has _new breaking changes_ that weren't on previous versions of iOS 14, and which will require significant effort on your part to fix, you're suddenly in a race against the clock. A lot of us pulled all-nighters, and there's still no guarantee we'll be able to launch today, because App Review can take quite a bit of time, even when they're rushing through the process as fast as they can.
We had to come to terms very quickly with the fact that Apple seems to have excluded us from the launch window almost entirely this time. Meanwhile, larger companies or organizations that have business models less dependent on interests from passionate iOS users will not really see as much impact — although quite a few small things in iOS 14 did break some of those apps, and they're probably rushing to get critical updates out as well.
When you have less than 24 hours after receiving a version of the software required to submit your app that has _new breaking changes_ that weren't on previous versions of iOS 14, and which will require significant effort on your part to fix, you're suddenly in a race against the clock. A lot of us pulled all-nighters, and there's still no guarantee we'll be able to launch today, because App Review can take quite a bit of time, even when they're rushing through the process as fast as they can.
We had to come to terms very quickly with the fact that Apple seems to have excluded us from the launch window almost entirely this time. Meanwhile, larger companies or organizations that have business models less dependent on interests from passionate iOS users will not really see as much impact — although quite a few small things in iOS 14 did break some of those apps, and they're probably rushing to get critical updates out as well.
That's what the majority of users do anyway. It probably takes two weeks just to hit 25% adoption of a new OS.
Exactly! People are acting like you could have just developed for beta 1 and smooth sailed through the summer. One of the betas changed how items in my toolbar were ordered. The next beta swapped them back to the way they were. You need to time to debug everything in each beta release. I know more than one person that pulled an all nighter last night trying to scramble with the one day's notice.
Ok, so I read more of the thread and it's a timing issue in terms of releasing updates via various builds. I still want someone to explain why we have a Beta process in the first place. The whole point of Beta is to test the IOS program for bugs, provide feedback, and start working on app updates while the beta process is in motion. Apple even says don't download this on your main phone because it might do damage to the main phone. Basically, from the day WWDC happened to now, developers had some sort of program for the new IOS update. I would think it's like writing a semester long paper for school. You get the assignment on day one, the teachers tells you when it's due, and unless you procrastinate, you are working on that paper the entire semester and the good students would try to get it done early so they don't need to worry about rushing it with a day or two left.
You have recently made numerous dubious and pointless comments but this one is in the running for the gold medal.