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
When opening the chat in one of our React Native apps in production some users receive an error (see image below). Our error logging/reporting doesn't catch any crashes/exceptions. I would assume this would be a 500 error from the API or something related to that. It happens occasionally but not for all devices/users.
I was wondering how one could figure out what is going wrong? Would be nice for our error reporting that if something went wrong on the TalkJS side that our system notifies us about this as well. I couldn't find anything about that in the docs. Maybe I missed something. For example add a callback which you could configure to send something to Sentry.
We currently don't have an onError handler available, I'll forward that request internally!
A general something went wrong, usually indeed indicates a non success code from the API.
Do you happen to know if there was a specific time-frame when these errors were reported and if these errors are persistent or fairly quickly were resolved?
On a side note, we'd usually recommend reaching out via our live support , we usually reply a bit faster over there.
When opening the chat in one of our React Native apps in production some users receive an error (see image below). Our error logging/reporting doesn't catch any crashes/exceptions. I would assume this would be a 500 error from the API or something related to that. It happens occasionally but not for all devices/users.
I was wondering how one could figure out what is going wrong? Would be nice for our error reporting that if something went wrong on the TalkJS side that our system notifies us about this as well. I couldn't find anything about that in the docs. Maybe I missed something. For example add a callback which you could configure to send something to Sentry.
Besides this, do you maybe know what is causing some users to see the following error?
The text was updated successfully, but these errors were encountered: