Is it now possible to start a download in safari and move on to other apps for a period of time and then come back to safari and see some progress? Or does it put the app to sleep like in previous iOS versions?
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.
Does iOS 11 allow for longer background tasks?
- Thread starter sdz
- Start date
- Sort by reaction score
I'm not entirely sure, but havent's noticed any difference. And I think it's RAM related: once the RAM is over, the app goes to sleep and the download is lost.
I wonder if keeping the app at the right side of the screen after calling it in the new window-based multitasking can make a difference
No, please can somebody with Development-Background comment?
Its a fact: You run Safari, download something, go back to homescreen and boom download stops.
You have a webchat in Safari open. You go back to homescreen and boom you will be kicked out of chat due to inactivity.
And this is with every app. The apps in iOS 10 have a "life" timespan betwwen 2-4 mins I guess. iOS somehow manages this and kills connections after a certain period of time.
WIll this be less strict in iOS 11 ?
Its a fact: You run Safari, download something, go back to homescreen and boom download stops.
You have a webchat in Safari open. You go back to homescreen and boom you will be kicked out of chat due to inactivity.
And this is with every app. The apps in iOS 10 have a "life" timespan betwwen 2-4 mins I guess. iOS somehow manages this and kills connections after a certain period of time.
WIll this be less strict in iOS 11 ?
Hi, I have a development background but only a cursory interest in iOS development. Feel free to ignore my input if it's not up to standard, especially as I don't really answer your questions!
One thing to mention is that background downloads for third party apps are possible through the URLSession API. While an app is more or less immediately suspended when backgrounded, downloads, uploads and file transfers can continue if managed through this API. There will be system imposed limits to this though. I don't think it's possible to determine precisely what these are. I'm not aware of any changes to limits in iOS 11, but there are some changes to the API discussed here. I wonder about the veracity of your claim that disconnects happen in 'every app' - perhaps not all are using this API?
Safari, being a first party app, obviously isn't restricted to this API. I'm not aware of changes in iOS 11 regarding maintaining http connections in background Safari tabs.
What I am facing is that apps that are in the background lose their connectivity after some minutes. Must downgrade to 10.3.3 because I need one specific app to constantly be in the background.
That is normal behaivor under iOS.
So I only can hope, that Apple changed / changes something in the architecture.
Background App Refresh doesn't let the app run constantly. It allows the app to be "woken up" at intervals to ensure the next time you use it it's up to date. Definitely doesn't allow it to run constantly.No, this is not normal behaviour under iOS. This is why we have Background App Refresh. And this is not working just since two betas.
True that. I used wrong words, it seems. There is an app, Jio 4G Voice. This is a Dialer app - allows users on 5S to receive calls on the Jio network for phones that do not natively support VoLTE. So, I fancied that it allows apps to "stay connected" in the background - hence I incorrectly used "run constantly".
Any advice? I am almost about to restore to 10.3.3 begrudgingly. This worked perfectly till beta 2.
Ah, that sounds more like CallKit / Core Telephony APIs... Could be that their app needs to be updated to work properly in iOS 11?
You are most likely right, but who knows! These guys did release an update two days ago that was "bug fixes", but I can't possibly expect an iOS compatibility update from them until Apple officially releases the software. I know many developers take that stand - they will release full new iOS compatibility only post public release of iOS. I understand them. One of the apps I use (forgetting the name) had an update couple of days ago that specifically mentioned compatibility with iOS 11 beta and I was mighty surprised - I used to think Apple didn't quite allow developers to bring out next version updates till the public release. A telecom network needs to be proactive!
Anyway, a minor niggle.Right now the only option is to restore back to 10.3.3 for pap's 5s.