Our client iOS apps open websocket connections with our servers.
We've noticed that despite clients force quitting our app, the server continues to receive HTTP requests from the client devices.
Our reconnection logic is set so as to immediately attempt to reconnect on connection drop. We do not explicitly disable this behaviour when the app is about to be closed as we figured the websocket connection would close and no further requests could be made once force closed.
Is it possible that the OS keeps some processes alive despite the app being force-quit?
Thanks!
We've noticed that despite clients force quitting our app, the server continues to receive HTTP requests from the client devices.
Our reconnection logic is set so as to immediately attempt to reconnect on connection drop. We do not explicitly disable this behaviour when the app is about to be closed as we figured the websocket connection would close and no further requests could be made once force closed.
Is it possible that the OS keeps some processes alive despite the app being force-quit?
Thanks!