You can feel the anticipation in this crowd! Incoming update, everyone take cover and protect your devices.
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.
Apple Releases iOS and iPadOS 13.2.2 With Fix for Background Refresh Bug
- Thread starter MacRumors
- Start date
- Sort by reaction score
Well, the updates are usually in the range of a few hundred MB and often even less than a hundred MB, so they are certainly not full installs (which are in the range of a few GB).
What issue?
They probably used the beta to test the new code but wanted to backport it to 13.2 since a lot of people were pissed off about it. 13.3 beta has other changes that are likely not ready yet.
Has anybody done enough testing with the relevant Beta to know precisely what the Background App "Kill Timer" is set to (by iOS) ???
IMO, the addition of this Timer is the most-important change for this iOS update, by far !
IMO, the addition of this Timer is the most-important change for this iOS update, by far !
Already installed for me.
[automerge]1573151788[/automerge]
Same as 13.0, 13.1... great battery life as usual.
Took them about a week to bring out a fix. They must've been on to it quickly. There are too many bugs around, but it's good that they fix the big ones quickly (presuming they have done here). Must be quite a difficult and pressurised job working on iOS.
These days Apple just shoves whatever is in the repository out when Cook's marketing schedule calls for a release; tested or not.
Old way: internal testing reveals bugs which are prioritized by their impact on functionality and usability.
Modern way: bugs are prioritized about how many reports and votes they get from public beta testers
Apple's new social way: bugs and hardware issues are fixed when they get significant media attention
So every new release of a major iOS version should be absolutely perfect and require no further updates? There’s a really simple solution for you if you’re torked off over the number of releases. Don’t update and learn to love with the bugs you have currently.
No, his complaint is about way too many releases. At least Microsoft limits themselves to once per month on a predictable schedule. How would you like it if your phone and desktop had to go down 30 minutes every day due to updates?
There's a disruptiveness factor too: see the complaints about Windows requiring a full OS upgrade every 6 months as well.
You're justifying releasing buggy software as long as they fix it later. We want things done right, or not shipped.
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?
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.
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.
Probably because it did not impact the wide customer use cases. I could never get the "bug" to trigger for me at all, and therefore even questioned if this was just made up. Apparently, it is a subset of apps or processes (of which I have not yet read an article of what these are). But it was somewhat irresponsible to portray this as a widespread problem impacting every activity. Like I said, never got it to trigger for me even with a boatload of apps open. I did read one complaint that articulated that it happened during a background download. So perhaps that is one process impacted.
I don't know which devices you have or what sizes you're seeing, but this update was under 150MB for some folks - me included on an iPhone 11.
Looks like I have to deal with Messages bug (only showing email addresses and not phone numbers for some contacts) for a while longer.
It is very frustrating to type in a persons name and only get email addresses to choose from.
It is very frustrating to type in a persons name and only get email addresses to choose from.
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?
Well. 13.3 fixed the app refresh bug (whatever you call it) and another bug for me where clipping of screen dump was not saved until you did second screen dump. Not sure what other fixes 13.3 did. But my 11 Pro Max was on just official 13.2 release as I did not want my new toy on the beta program. Installed fine for me as well. Initial testing shows bug fixed on app refresh but then I noticed it more on iPad Pro than my 11 Pro Max anyway
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.