Thank you for your prompt response.

I would like to clarify a few points, please correct me if I’m wrong: When a user "force quits/kills" the app by swiping it up, the background process will terminate. Any ongoing uploads will stop, and we cannot initiate new uploads in the background until the user relaunches the app. After the app is "force quit/killed" by swiping up, is there any way to resume the app and start uploading again via notifications? I’ve noticed apps like WhatsApp and iPhone's Photos app seem to sync data in the background even after being "force quit/killed" by the user. If they manage this, it suggests there might be a special API at Apple’s side that allows this functionality, but it doesn’t seem to be public. Is there a special API available that enables background file uploads (similar to the Photos app) after a user force quits the app(by swipe up)? If so, how can we gain access to it? We are developing a medical application specifically for Parkinson's patients. The app uploads exercise videos to the server for analysis of the exercise results. If you require more details about our app to evaluate whether we can access such an API, please let me know, and I’ll provide further information. Additionally, if we have 5 to 10 video files that need to be uploaded to the server. What would be the best approach for this? Should we upload the videos in parallel (i.e., upload all files simultaneously)? Or, should we upload them sequentially (one by one)? Based on my findings, when the app is in the background and a new task like an upload is initiated, there is a "rate limiter" that can cause increasing delays with each task. I came across this in the following discussion: Apple Developer Forums. Please advise on the best approach.