Replies: 4 comments 6 replies
-
What does your With something like so you can add the digest to tags // error.js
"use client";
import * as Sentry from "@sentry/nextjs";
import NextError from "next/error";
import { useEffect } from "react";
export default function GlobalError({
error,
}: {
error: Error & { digest?: string };
}) {
useEffect(() => {
Sentry.captureException(error, { captureContext: { tags: { digest: error.digest } } });
}, [error]);
return (
<html>
<body>
{/* This is the default Next.js error component but it doesn't allow omitting the statusCode property yet. */}
<NextError statusCode={undefined as any} />
</body>
</html>
);
} |
Beta Was this translation helpful? Give feedback.
-
First of all, As I found I tried both
And in the Sentry I see this as log which canny no beneficial information |
Beta Was this translation helpful? Give feedback.
-
I have opened a discussion here vercel/next.js#60283 |
Beta Was this translation helpful? Give feedback.
-
@AbhiPrasad Is there any alternative way to show the user a UUID as a tacking id and tag the SSR error using the same UUID? |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Next.JS adds a
digest
to the error object and shows it in the the default error page.I would like to ask how can I find the reported bug based on the
digest
value?I tried to add a tag in the
beforeSend
but unfortunately thedigest
value is not available in thebeforeSend
hookBeta Was this translation helpful? Give feedback.
All reactions