Sendbird version: 3.0.144
Way of usage: React SPA
Overview what we are doing:
- For authentication we are using session tokens with day long expiration.
- We rely in one part of application on
onTotalUnreadMessageCountUpdateduser event handler. For that we connect user almost on the start.
- Interactive usage of sdk (for example sending messages, marking as read) is a bit deeper in the web app. To have it fully operational before connecting we are also creating SessionHandler, ChannelHandler and ConnectionHandler.
- Atop of that we have functionality that allows user to “archive” group chat. It can be triggered by any member of the chat, goes through our server, which uses sendbird platform API. First it freezes the channel and then deletes it.
Taking this all together: we create all handlers in the beginning and then we are connecting with sdk. It can happen that for most of the time we are only listening to the events. In meantime channels for the specific user can be removed.
Problem: We get a tons of errors which obfuscate our error log. Functionality is not affected directly, however we cannot go to production with so many false positives.
Thanks for help