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
We use the CourierProvider component, along with the Toast and Inbox. We have noticed that our users are getting a lot of "Courier Websocket errors" as console errors. It seems to happen when they leave the browser tab open for a long time and possibly if they're connectivity is patchy.
My guess as to what is happening is that the websocket loses connection when the user's device goes to sleep, but is then not able to reestablish that websocket connection when it opens back up.
As far as I can tell, this impacts the Toast component. Once the error has been observed, new notifications don't trigger a toast pop-up until the browser page has been refreshed. The Inbox seems to work just fine.
Here is an example of such a message (I've edited it to redact the client key)
We use the
CourierProvider
component, along with theToast
andInbox
. We have noticed that our users are getting a lot of "Courier Websocket errors" as console errors. It seems to happen when they leave the browser tab open for a long time and possibly if they're connectivity is patchy.My guess as to what is happening is that the websocket loses connection when the user's device goes to sleep, but is then not able to reestablish that websocket connection when it opens back up.
As far as I can tell, this impacts the
Toast
component. Once the error has been observed, new notifications don't trigger a toast pop-up until the browser page has been refreshed. TheInbox
seems to work just fine.Here is an example of such a message (I've edited it to redact the client key)
Has anyone seen this before and/or can help with this? Thanks!
The text was updated successfully, but these errors were encountered: