Whet the application gets terminated in the background by the iOs, then there is no reason to keep any connections open, am I right? As there would be app launch again, where the application would start the connections again.
So it somehow feels correct to call
ParseLiveQuery.getDefault()?.close()
in
func application(_ application: UIApplication, didDiscardSceneSessions sceneSessions: Set<UISceneSession>)
I am just not sure if that is enough to close everything as I see after trying it in sceneDidEnterBackground
testing LiveQuery isConnected: Optional(false)
testing LiveQuery isConnecting: Optional(false)
testing LiveQuery isSocketEstablished: Optional(true) ← this has any effect or is the connection closed on server side with no hanging resources?
testing LiveQuery isSubscribed: Optional(true) ← this is probably due to cached queries and has to effect
testing LiveQuery isPendingSubscription: Optional(false)
Of do I again understand it wrong and the application actually do not open a new connection on the next launch if there is previous connection still available? I am confused if this might happen as the application gets terminated.
And as I tried also without terminating application, just putting in background and back active, I can’t somehow re-open the connection:
- ParseLiveQuery.getDefault()?.close()
- testing LiveQuery isConnected: Optional(false)
- ParseLiveQuery.getDefault().open(completion: { error in
print(“error while opening webSocket: (error?.localizedDescription)”)
}) - testing LiveQuery isConnected: Optional(false)
isConnected stays false even the .open() do not throw any error
I was thinking about following strategy to handle bad connectivity:
- on app launch fetch all data to get up-to-date and subscribe LiveQuery
- to detect bad connectivity
- on 3x failed
.save()of.fetch()inform user with manual “retry” button and when there is success after manual trigger later the application should check if LiveQuery is still life. If not, try to restart like a fresh app launch - sending
Date()value in.save()context and reject the save inbeforeSavecloud code if object’supdatedAton server is newer than value of the pending save → this prevents outdated saves and inform client that there was some updates missed → if data were missed, client app would again fetch and restart LiveQuery
- on 3x failed
But here I am not sure how to restart or close LiveQuery in a clean way as the above isConnected stays false and isSocketEstablished stays true
What I am trying to achieve is to primary not drain server resources through some zombie webSockets opened, because outdated state on device is not critical as the server can reject outdated save operation