Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
My concern is with the OS numbering. Are we going to have a 13.x release post-13.4? Usually 1x.2 releases are meant for mid to late December, while 1x.3 releases are reserved for a March/April release. 1x.4 are the final updates/security fixes for legacy devices that won’t be compatible with the upcoming iOS release in September.
There's really no particular set schedule for releases. What you are describing is some general takes on how it has happened in some recent years, but certainly not always by far--there used to be versions where things wouldn't even get past x.1 release basically.
 
  • Like
Reactions: jonblatho
Doesn't seem like there's any justification really going on, just commentary.

Does Microsoft have a phone out that consumers use on a constant basis basically?

Microsoft has an OS for desktops, servers, and cloud and office suite with far more moving parts that interfaces with tens of thousands of pieces of third-party hardware and drivers. Microsoft maintains compatibility with programs written 30 years ago.

Apple has a handful of first-party phones that can't run software more than 4 years old.

The value proposition from Apple was to put up with more expensive hardware and breaking old programs for an overall better user experience. Was.
 
Thank god. From now on I'll keep my devices on the last summer update until the next major release has been out for at least a couple of months and most major issues have been ironed out.
 
  • Like
Reactions: MadeTheSwitch
Finally....weren't we supposed to start getting Delta updates as of iOS 5? None of these feel very delta-y.

This is exactly that. Before iOS 5 we had to download the entire OS each time a new version came out which nowadays is in the gigabytes range. Today were downloading a “piece” of the OS which in this case comes out to just about 100MB and we’re able to do this on the device wirelessly rather than plugging the device into a Windows or Mac machine to download and install the update as we used to before iOS 5.
 
Looks promising. Tried several safari tabs, youtube, instagram, took some pictures, returned to safari and YouTube, everything stayed in memory. Left phone idle for 10 mins. Reopened everything and still in memory.
Hopefully it’ll stay that way.
 
  • Like
Reactions: Ghost31 and adamrc
It's appreciated they fixed it, but come on.

How many times have we updated since September? I think it's three or four times now. It's a pain in the (rhymes with sass).

I still haven't updated my watch to the latest point release because I don't want to wait for 40 minutes.

Finally....weren't we supposed to start getting Delta updates as of iOS 5? None of these feel very delta-y.
you can always give the update a few weeks to see how it is going before participating, no one forces you to rush (as you are aware by putting off the watch OS update). Personally, I am on Public Beta and have been for a long time, doesn't bother me at all. I also mysteriously am not impacted by all these "bugs" people report. I clearly am not using it the same way others are I guess. But I would sure be glad to get any bug fixed quickly.

Oh, and the full iOS download is about 5 gb I think, so anything much smaller than that is an incremental download, yah?
 
The only reason for beta releases is to get blogs and news site to talk about how responsive and engaged Apple is.

For those that can't read between the lines that means beta releases only serve a marketing purpose and have absolutely no impact on software quality. Ok, maybe "no impact" is extreme as I'm sure if the beta falls over completely, Apple will take note. However, I don't expect Apple does anything with Beta bug reports.

How do we know Betas are marketing only? It is simple, if beta releases were for testing and QA they would include release notes that detail what was changed and should be tested. Apple does not do this! Why? Because it looks bad to marketing.

How to do we know Apple ignores Beta bug reports, because so many major bugs are released after being reported.

All that's needed here to understand how Apple operates is some common sense.
Theorizing is fun and all, but simpler realistic information still ends up applying: the main reason for beta releases has been for developers to test their apps against them. Things were expanded to the public later on to get more logs and information from a larger variety of devices, configurations, and usage patterns.
 
Looks promising. Tried several safari tabs, youtube, instagram, took some pictures, returned to safari and YouTube, everything stayed in memory. Left phone idle for 10 mins. Reopened everything and still in memory.
Hopefully it’ll stay that way.
that's exactly the same way my iPhone was before the update, must be something else that triggered the issue
 
Can someone explain to me how I can download app updates of any size over cellular, but not this software update which is 138 MB?
The number of people who might jump on at the same time on an iOS update is quite a bit different than some app update.
 
Looks promising. Tried several safari tabs, youtube, instagram, took some pictures, returned to safari and YouTube, everything stayed in memory. Left phone idle for 10 mins. Reopened everything and still in memory.
Hopefully it’ll stay that way.

To all those saying it was a feature, not a bug - lol!

Even Apple isn't that ridonculous!
 
  • Like
Reactions: Ghost31 and IG88
Microsoft has an OS for desktops, servers, and cloud and office suite with far more moving parts that interfaces with tens of thousands of pieces of third-party hardware and drivers. Microsoft maintains compatibility with programs written 30 years ago.

Apple has a handful of first-party phones that can't run software more than 4 years old.
How does that relate to them doing monthly updates vs. other companies pushing out updates as they have them and feel they need to be released?
 
Using the 13.3 beta, haven't actually gone so far as to do an actual time test on the background process kill time, but it sure as heck is improved and seems to be back to normal.
For instance, if I did a search in Amazon on 13.2 and left the app, even for a couple of seconds, when I returned the app would reload and the search gone.
After installing the 13.3 beta though, I did the same test and well, two days later if I go back into Amazon, the same search results are still there. That's more like it.
maybe it was something in the Amazon app that triggered the issue, or did you do an amazon search through a browser? This same scenario through Safari, did not cause me problems
 
It's appreciated they fixed it, but come on.

How many times have we updated since September? I think it's three or four times now. It's a pain in the (rhymes with sass).

I still haven't updated my watch to the latest point release because I don't want to wait for 40 minutes.

Finally....weren't we supposed to start getting Delta updates as of iOS 5? None of these feel very delta-y.

Your devices would update at nighttime (while you sleep) if you have automatic updates turned on, the devices are charging, and connected to WiFi. there's no waiting for you. No pity either. 🤣
 
How does that relate to them doing monthly updates vs. other companies pushing out updates as they have them and feel they need to be released?

Nothing. You're putting words in my mouth, probably because you didn't follow the thread. It has to do with Microsoft releasing stable software and minimizing update disruption, not Apple's constant panic to get software out before new hardware is put on sale, and then releasing tens of tiny updates to fix things that broke in the rush.
 
Has it been pulled? I’m on 61% battery and even with the charger connected my ‘Install Now’ button is greyed out...

B55F8AB2-C925-47F9-A312-F0A68C251991.png
 
The question is, if this is going to fix the bad memory management... background app refresh is just a symptom of the problem... => You can have only Safari open and it will unload tabs much quicker than it does on iOS 12. Nothing to do with background refresh. However, when running out of memory, iOS will first kill background apps of course.
That said, much like on Windows and macOS, I would prefer a lot to put memory management into the hand of the user. I.e. have active in the taskbar. Suspend them by swiping down (greying out their preview) and swiping up to kill them (like now). iOS should only be allowed to suspend apps after x minutes of inactivity and kill apps after y minutes of inactivity. x and y to be user-set. Auto-Suspend (like now) should be user selectable. I'd much appreciate if it would just auto-kill them after like 60 minutes...
While on it: 6-8GB of RAM would be nice to keep some apps alive. There's no logic reason against it...
 
Somehow the Beta testing isn't uncovering a bunch of issues and when the release goes public they show up. So in a sense we are all at fault if not testing or reporting.
 
What that hell is the point of the beta release then

In a lot of software, the first number denotes a major version, the second a minor version, and the third a patch (e.g. bug fixes or addendums). Sometimes you might see additional flags to denote alphas or betas. Apple tweak this approach and often hold larger features for minor versions that others might consider worthy of a major version.

So the beta is to test a new minor version, but this is a patch.

If you want to get really in the weeds on software versioning, semver.org is a good resource.
 
If it means anything, I was getting frequent jetsam (low memory warnings for apps) events when using my phone (several an hour) on iOS 13.2 and now on .2 I haven't had a single one since the update almost an hour ago.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.