Skip to content

errors in remix loaders/actions on vercel aren't reportedΒ #13825

@boertel

Description

@boertel

Is there an existing issue for this?

How do you use Sentry?

Sentry Saas (sentry.io)

Which SDK are you using?

@sentry/remix

SDK Version

8.31.0

Framework Version

[email protected]

Link to Sentry event

No response

Reproduction Example/SDK Setup

https://github.com/boertel/sentry-action-error/

a few tests that I did:

  1. build the app locally (with npm run build and npm run start) and the errors are reported
  2. print DSN to make sure Sentry was properly setup
  3. trigger manually captureException which doesn't work

Steps to Reproduce

  1. deploy repo to vercel
  2. set VITE_SENTRY_DSN as an environment variable
    2 access the page /sentry-example-page
  3. click "throw an error on the action!"

Expected Result

Expected behavior is to see: "Sentry Error" on my Sentry Issues

(I do see a Unexpected Server Error but it is reported by https://github.com/boertel/sentry-action-error/blob/main/app/root.tsx#40 on the client side)

Actual Result

error is not showing in my Issues

Metadata

Metadata

Assignees

No one assigned

    Labels

    BugPackage: remixIssues related to the Sentry Remix SDK

    Projects

    Status

    No status

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions