Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Catch TalkJS errors client side for error reporting #393

Open
dees040 opened this issue Apr 5, 2023 · 1 comment
Open

Catch TalkJS errors client side for error reporting #393

dees040 opened this issue Apr 5, 2023 · 1 comment

Comments

@dees040
Copy link

dees040 commented Apr 5, 2023

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.

new Talk.Session({
  appId: 'YOUR_APP_ID',
  me: me,
  onError: (e) => Sentry.captureException(e),
});

Besides this, do you maybe know what is causing some users to see the following error?

image

@MattivdWeem
Copy link
Contributor

Hey @dees040

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants