You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If ChatClient is not needed or we want to free up all underlying channels before closing the app, browser tab, chatClient.close will release all channels.
Currently, devs need to iterate over each channel and release it explicitly. This will also include unregistering subscription callbacks.
Point is, close should free up all those resources in one explicit call.
free up all underlying channels before closing the app
Do you mean if the app shuts down entirely, or if it simply goes into the background / the chat component is closed? I presume the latter, as in the former case, freeing everything up happens by virtue of quitting the app / closing the browser tab.
Currently, devs need to iterate over each channel and release it explicitly
To be clear, you're referring to each room, as a group of channels pertaining to a chat room, rather than individual realtime channels?
We'll need to think about this one a bit more and its use-case - my preference would be to defer it for now so as to avoid adding complexity to the room lifecycle (notwithstanding any future requests for the functionality).
chatClient.close
willrelease
all channels.close
should free up all those resources in one explicit call.┆Issue is synchronized with this Jira Task by Unito
The text was updated successfully, but these errors were encountered: