Are CORS console errors thrown by the browser ignored by Sentry?

[vishnusankaran-plivo]

Does sentry not log the errors thrown by the browser like the CORS errors, like below?

Access to fetch at 'https://so-and-so.com/so-and-so-path' from origin 'https://sellular.com/so-and-so' has been blocked by CORS Policy. No `Access-Control-.....` header is present in the requested resource. ...

[AbhiPrasad]

Hey! Generally we don't grab errors from the console unless you turn on the CaptureConsole integration: https://docs.sentry.io/platforms/javascript/configuration/integrations/plugin/#captureconsole

[vishnusankaran-plivo]

Hey, Thanks Abhi for the answer. Let me check this out!

[vishnusankaran-plivo]

@AbhiPrasad Hi Abhi, we have configured the CaptureConsole integration. All the console errors are getting captured in Sentry, although we don't see CORS errors being captured. Do you see any particular reason for this?

[lforst]

Hi, the CaptureConsole integration only instruments the usage of console.log and so on. When a CORS error happens, the browser prints it to the browser console, but doesn't actually call console.log. This is why the integration doesn't pick it up.

I believe it is actually by design and for security reasons that JS cannot distinguish between network errors and CORS errors and therefore it is sadly not possible for the SDK automatically pick up CORS errors.

[vishnusankaran-plivo]

Thanks a lot, Luca! That confirms my assumption 👍