Become a MacRumors Supporter for $25/year with no ads, private forums, and more!

foxracing

macrumors newbie
Original poster
Dec 28, 2009
13
0
When you push on the icon of the app you want to delete from the multitasking menu no x comes up to delete it .... Did apple not get to that in this beta or am I not seeing something?
 

MLG

macrumors regular
Jul 17, 2012
112
0
Swipe them away...the same way it has been on Android for several years.
 
Comment

C DM

macrumors Sandy Bridge
Oct 17, 2011
51,388
19,437
Does that really close the apps though? I seem to do this, but then if I open at least some of the apps, they are back to where they were before I closed them, as if they didn't really get closed anyway.
 
Comment

mikeo007

macrumors 65816
Mar 18, 2010
1,373
122
Does that really close the apps though? I seem to do this, but then if I open at least some of the apps, they are back to where they were before I closed them, as if they didn't really get closed anyway.

That's good programming by the app developers, coupled with Apple's excellent background processing APIs. In iOS 7, this will be even better with the new background APIs.
 
Comment

C DM

macrumors Sandy Bridge
Oct 17, 2011
51,388
19,437
That's good programming by the app developers, coupled with Apple's excellent background processing APIs. In iOS 7, this will be even better with the new background APIs.
Not really sure. I mean if I want to actually close and restart an app, how would I do it? In iOS 7, doing this doesn't really seem to do it, even using the force quit method doesn't seem to do it, so no way to really fully restart an app (at least most/some of the apps) in iOS 7?
 
Comment

mikeo007

macrumors 65816
Mar 18, 2010
1,373
122
Not really sure. I mean if I want to actually close and restart an app, how would I do it? In iOS 7, doing this doesn't really seem to do it, even using the force quit method doesn't seem to do it, so no way to really fully restart an app (at least most/some of the apps) in iOS 7?

Clicking that 'X' in iOS 6 sends the kill signal to the app. The same will be true of swiping up an app in iOS7. At that point, the app has to free up its resources. If the developer chooses to save the app state at this point, then they can restore the app in exactly the same state as you left it. The user doesn't have control over this, it's a developer decision.
 
Comment

C DM

macrumors Sandy Bridge
Oct 17, 2011
51,388
19,437
Clicking that 'X' in iOS 6 sends the kill signal to the app. The same will be true of swiping up an app in iOS7. At that point, the app has to free up its resources. If the developer chooses to save the app state at this point, then they can restore the app in exactly the same state as you left it. The user doesn't have control over this, it's a developer decision.
As far as freeing up resources, perhaps that's the primary and maybe the only part of it now. That said, there is a way to kill/restart an app fully in iOS 6, at least with a force quit (using the sleep/lock and home buttons), but in iOS 7 even that doesn't cut it.

For example, take App Store, you have some updates that installed and now simply show up as having been installed and new ones aren't being checked for. There's no refresh there. In iOS 6 you can close the app or even force quit it and start it again and it will start fresh and clear and run a check for updates. In iOS 7 that doesn't happen--the app is where it was with all the information that it had no matter if you swipe it away or force quit it.
 
Comment

Stetrain

macrumors 68040
Feb 6, 2009
3,548
18
There's really no reason to remove apps to 'free up resources'.

It's really only there in case an app has glitched out and you want to reset it to a clean state.
 
Comment

C DM

macrumors Sandy Bridge
Oct 17, 2011
51,388
19,437
There's really no reason to remove apps to 'free up resources'.

It's really only there in case an app has glitched out and you want to reset it to a clean state.
Yup, that's one of the main things I would use it for whenever I would actually use it. And that seems to be the main thing that doesn't seem to be working now in iOS 7, at least with some (perhaps Apple's default), if not most of the apps.
 
Comment

Vol7ron

macrumors 6502
Jun 11, 2009
281
189
Derry, NH
It's definitely a lot more fluid to close an app then iOS 6 and previous...Although now I notice that you have to click the home button or select a running app to exit this mode. Not that this is really an issue, but I was just to just being able to tap the screen to exit multitasking mode..
 
Comment

Stetrain

macrumors 68040
Feb 6, 2009
3,548
18
Yup, that's one of the main things I would use it for whenever I would actually use it. And that seems to be the main thing that doesn't seem to be working now in iOS 7, at least with some (perhaps Apple's default), if not most of the apps.

Seems to work for me with a couple of third party and Apple apps (Messages, Music, Safari) that I just tried.

They may still remember which page you were on and go there, but you can tell that it's loading the app again rather than just resuming it.
 
Comment

mikeo007

macrumors 65816
Mar 18, 2010
1,373
122
As far as freeing up resources, perhaps that's the primary and maybe the only part of it now. That said, there is a way to kill/restart an app fully in iOS 6, at least with a force quit (using the sleep/lock and home buttons), but in iOS 7 even that doesn't cut it.

For example, take App Store, you have some updates that installed and now simply show up as having been installed and new ones aren't being checked for. There's no refresh there. In iOS 6 you can close the app or even force quit it and start it again and it will start fresh and clear and run a check for updates. In iOS 7 that doesn't happen--the app is where it was with all the information that it had no matter if you swipe it away or force quit it.

What your calling "force quit" is actually rebooting the phone. I'll say it again, this action, or swiping the apps off the screen will both kill the app. Any sort of state saving that your experiencing when re-launching a closed app has been put in there by the developer. There is no fundamental difference between killing apps in iOS6 and iOS7.
Your app store issue sounds like a bug. Since updating happens differently in iOS7, I wouldn't immediately presume that it works the same. Regardless, if you kill off the app by swiping it up, you ARE forcing it to reload. What happens at that point depends on how the app was designed. Apple's apps also don't always follow their own rules, and do sometimes have excess processes that run outside of the actual app itself.
 
Comment

aristobrat

macrumors G5
Oct 14, 2005
12,278
1,382
That said, there is a way to kill/restart an app fully in iOS 6, at least with a force quit (using the sleep/lock and home buttons).

What your calling "force quit" is actually rebooting the phone.
No joke.

Holding down the sleep/wake and home buttons is about the equivalent of walking up to a PC that's turned on, yanking out the power cord (without having shutting it down first), and then plugging the power cord back in. :eek:
 
Comment

C DM

macrumors Sandy Bridge
Oct 17, 2011
51,388
19,437
Seems to work for me with a couple of third party and Apple apps (Messages, Music, Safari) that I just tried.

They may still remember which page you were on and go there, but you can tell that it's loading the app again rather than just resuming it.
For me it pretty much instantly seems to go exactly to the place where I left off in majority of those cases, without any delay or anything to indicate that it was even doing anything in the background.

----------

What your calling "force quit" is actually rebooting the phone. I'll say it again, this action, or swiping the apps off the screen will both kill the app. Any sort of state saving that your experiencing when re-launching a closed app has been put in there by the developer. There is no fundamental difference between killing apps in iOS6 and iOS7.
Your app store issue sounds like a bug. Since updating happens differently in iOS7, I wouldn't immediately presume that it works the same. Regardless, if you kill off the app by swiping it up, you ARE forcing it to reload. What happens at that point depends on how the app was designed. Apple's apps also don't always follow their own rules, and do sometimes have excess processes that run outside of the actual app itself.
No joke.

Holding down the sleep/wake and home buttons is about the equivalent of walking up to a PC that's turned on, yanking out the power cord (without having shutting it down first), and then plugging the power cord back in. :eek:
Seems like there's a misunderstanding between force quitting and actually restarting. Yes, you can restart the phone by holding down both the sleep/lock and home buttons for a little while, but you can also force quit an app while you are in the app by first holding down the sleep/lock button until you get the message about turning off the phone to appear and then (after you let go of the sleep/lock button) holding down the home button for about 5-10 seconds until the app quits and you are back on your home screen.
 
Comment
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.