Can’t actually force quit/force kill apps

[CMak]

I searched to see if this had already come up, but I couldn’t find any results, so I apologize if it has and I just couldn’t find it.

In previous versions of iOS you could force quit an app and that app process would stop running. For instance, if you force quit Mail, you wouldn’t get new mail notifications unless you re-launched Mail because the Mail app process was no longer running. The same would be true for Skype, Slack, or other apps.

In iOS 11, that no longer appears to be true. I’ve read the posts on how you’re supposed to force quit apps now and am using those techniques, but even after force quitting an app the process continues to run and contact online services and generate notifications, which it should not be doing.

Has anyone else observed this? Does anyone know of a way to *actually* force kill apps in iOS 11?


—Chris

 

[serialiphoneuser]

Hold down the Power button until the Power off screen comes up. Hold down the Home button and the app should quit/restart. Wonder if there's a similar technique for iPhone X.

 

[Alrescha]

even after force quitting an app the process continues to run and contact online services and generate notifications

That is generally not how notifications work in iOS. Notifications are part of the OS and apps register with Apple's servers to subscribe. Apps do not need to be running. See: https://developer.apple.com/notifications/

Quitting apps works for me the same as it ever did, in that after I quit an app it clearly does not resume from where it left off (for those apps that do not maintain their state).

A.

 

[posguy99]

In iOS 11, that no longer appears to be true. I’ve read the posts on how you’re supposed to force quit apps now and am using those techniques, but even after force quitting an app the process continues to run and contact online services and generate notifications, which it should not be doing.

Does anyone know why you'd still be trying to force-quit apps on iOS 11?

 

[C DM]

I searched to see if this had already come up, but I couldn’t find any results, so I apologize if it has and I just couldn’t find it.

In previous versions of iOS you could force quit an app and that app process would stop running. For instance, if you force quit Mail, you wouldn’t get new mail notifications unless you re-launched Mail because the Mail app process was no longer running. The same would be true for Skype, Slack, or other apps.

In iOS 11, that no longer appears to be true. I’ve read the posts on how you’re supposed to force quit apps now and am using those techniques, but even after force quitting an app the process continues to run and contact online services and generate notifications, which it should not be doing.

Has anyone else observed this? Does anyone know of a way to *actually* force kill apps in iOS 11?


—Chris

Notifications could always come in (short of you disabling them) wether or not the related app is running. Pretty much always been like that.

 

[Newtons Apple]

Does anyone know why you'd still be trying to force-quit apps on iOS 11?

Because I feel better if they are no longer there.

 

[C DM]

Does anyone know why you'd still be trying to force-quit apps on iOS 11?

Same reasons you might want/need to do it in iOS versions prior to iOS 11. But that's not really what the thread is about.

 

[Alrescha]

But that's not really what the thread is about.

"Please don't feed the trolls"

 

[C DM]

"Please don't feed the trolls"

Aside from perhaps merely responding being considered "feeding" seems like I stayed away from that.

 

[Alrescha]

Aside from perhaps merely responding being considered "feeding" seems like I stayed away from that.

Alas, I am afraid that responding at all is just more grist for their mill. I just add them to the ignore list and move on.

A.

 

[rodrigo_pereira]

The same would be true for Skype (…)

Nope, VoIP apps use push notifications (they are a bit different from typical push notifications):

"In the past, a VoIP app had to maintain a persistent network connection with a server to receive incoming calls and other data. This meant writing complex code that sent periodic messages back and forth between the app and the server to keep a connection alive, even when the app wasn’t in use. This technique resulted in frequent device wakes that wasted energy. It also meant that if a user quit the VoIP app, calls from the server could no longer be received."