Apple releases iOS 13.2.2, iPadOS 13.2.2 with background app quit bug fix

2»

Comments

  • Reply 21 of 25
    However, this update still DOES NOT fix the GLARING rape of Apple TV app by iOS Content & Privacy Restrictions. Apple is sliding down the hill. >SMH<
     0Likes 0Dislikes 0Informatives
  • Reply 22 of 25
    JavoCB17 said:
    I stayed in iOS 13.1.2 since I haven’t had any issue with the phone. I really think many times in updating iOS as it fixes some issues but brings new ones which some of them could be really annoying.
    I stopped updating altogether. Unless there's a bug that really annoys me, I'm ok using the software the device came with. So, yeah, I'm running 13.0 on the 11 Pro.

    I did actually upgrade my MB to 10.15....just to see if much had changed. Since I only use that laptop for browsing, not much did change. Well, Safari tabs and history don't sync with iOS 12 and older Macs.

    Not that updating is a PITA, rather I don't want to have the bugs replaced by new bugs.

     0Likes 0Dislikes 0Informatives
  • Reply 23 of 25
    dysamoriadysamoria Posts: 3,430member
    terun78 said:
    I never understood why people complain about the updates. I spent a couple of years on Android and let me tell you, be thankful for swift updates. On Android if you wind up with some bugs it’ll take a while to get a fix and that’s if you get one. Only complain if the bugs aren’t getting fixed.
    Most of the bugs I report have NOT been fixed in SIX MAJOR REVISIONS.
     0Likes 0Dislikes 0Informatives
  • Reply 24 of 25
    While it has applied a band-Aid to iPadOS and made iPads usable again under iOS 13, this is fast from a real fix (ie addressing the underlying problem that causes the problem), as iOS on an iphone, when in CarPlay mode, becomes absolutely unusable after roughly 10-15 minutes, when using iPhone at the same time while CarPlay is running.

    The inherent problem is terrible memory management since iOS 7, which has gotten worse with each iOS revision. IOS is basically unable to maintain the state of an app in the background, and aggressively quits background apps, even those that it should NEVER quit, like Maps (while navigating), or the process handling copy/paste - and of course, open Safari tab (resulting in losing work and content when they reload).

    The solution would be implementing a swap file on iOS (like it is on Mac), which would effectively solve the issue, or go a long ways towards a solution. It sadly appears that those in charge of product managing iOS don’t actually have a clue about the technical aspects of Unix.
     0Likes 0Dislikes 0Informatives
  • Reply 25 of 25
    dysamoria said:
    terun78 said:
    I never understood why people complain about the updates. I spent a couple of years on Android and let me tell you, be thankful for swift updates. On Android if you wind up with some bugs it’ll take a while to get a fix and that’s if you get one. Only complain if the bugs aren’t getting fixed.
    Most of the bugs I report have NOT been fixed in SIX MAJOR REVISIONS.
    Hence me not updating altogether. No, it's not difficult, doesn't take much time, et cetera. But to have bugs replaced by new bugs...think I'll skip. I simply use the default x.0 that comes with every new iPhone and only update if there's a really important security update baked in.


     0Likes 0Dislikes 0Informatives
Sign In or Register to comment.