I have a request for modification in the Sendbird Flutter SDK and would like to inquire about it. Currently, when I modify the code and do a hot reload, a new Sendbird instance is created. However, there seems to be no way to disconnect and dispose of the instance at the platform level. This leads to an issue where the number of connections increases with each hot reload, potentially reaching the peak connection limit. Additionally, event listeners from the previous instances remain active, causing repeated event triggers and making it difficult to manage. I have only tested this on Flutter Web and haven’t confirmed if this happens on other platforms as well. Please consider either allowing only one Sendbird instance to be created at the platform level and ensuring it stays connected or providing an interface in Flutter to reference and dispose of existing instances. Thank you.
1 Like
