Note that there are some explanatory texts on larger screens.

plurals
  1. POUIRequiresPersistentWiFi equivalent for cellular connection
    text
    copied!<p>OK, so I specified a <strong>UIRequiresPersistentWiFi</strong> key of my App's plist to <strong>YES</strong> so the iOS won't stop fetching the data when my app is in the background.</p> <p>However, when the user uses cellular connection (not wifi) and my app is in the background, the download of the data is stopped after several minutes.</p> <p>I double checked the docs and it seems there is no equivalent of <strong>UIRequiresPersistentWiFi</strong> for cellular network that I could set.</p> <p>Is there any way I can make the connections over cellular network survive while the app is in the background? Any hints?</p> <p>Cheers!</p> <p><strong>Updates:</strong></p> <p>I am making an Internet radio app. Stream is combined with mp3s which I request one after another (can't request them in advance, can't change server side). It works when my app is in the background and uses wifi. However, when using cellular connection the network requests are not performed after some time spent in the background. There is no place for changing the strategy. The app is in the AppStore and it had worked before. I guess they changed something in the new version of the system.</p> <p>What is more I do not need throttling. My radio app has been already approved and is in the AppStore. The stream is sent with 128kb/s (that is the maximum) so that is not a problem. It looks like system silences my network requests (when on cellular network) after some time in the background. However, this only happens when I try to start the connection in the background.</p> <p>Description:</p> <ol> <li>App is in the background playing a mp3 streamed over cellular network. </li> <li>Mp3 ends </li> <li>I request the URL to another mp3 </li> <li>The request is not performed*.</li> </ol> <p>*works when using WiFi.</p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload