Error Handling? #182
-
I'm currently getting a lot of POST errors and timeouts with the magicbell-react component version(10.10.2) The problem is these bubble up my global "unhandled errors" function. Wrapping the react component in an error boundary does not stop this behavior. Is there a way I can swallow all the errors generated by the magicbell-react component? |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment
-
TLDR; This error is safe to ignore and we will fix this in an upcoming release. It's a case of rolling out an early API and using the wrong HTTP code to handle a common case. More detailsThat error is coming from your inbox integration. We're fetching the theme that you might have configured in our dashboard. The error message should be clearer, but its safe to ignore. There are two options to make it not error though:
{ |
Beta Was this translation helpful? Give feedback.
TLDR; This error is safe to ignore and we will fix this in an upcoming release. It's a case of rolling out an early API and using the wrong HTTP code to handle a common case.
More details
That error is coming from your inbox integration. We're fetching the theme that you might have configured in our dashboard. The error message should be clearer, but its safe to ignore. There are two options to make it not error though:
theme
,locale
, andimages
property to the sdk. This works, because we don't fetch the theme config when a config is provided in code. If