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>
);
} |
|
First of all, As I found I tried both And in the Sentry I see this as log which canny no beneficial information |
|
Please see: #6726 (comment) - this is a nextjs/react limitation, we need some API to be able to connect the errors. I recommend you reach out to Next.js/React maintainers and ask them for better support here. For now you should be able to use the tagged digest on the Sentry error to look it up in your logs somewhere. Not ideal, but we can't instrument anything if it's not exposed. |
|
@AbhiPrasad Understood! When I use |
|
I have opened a discussion here vercel/next.js#60283 |
|
@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? |
|
We need some kind of tracing API to connect backend/frontend - maybe @lforst knows better here? |
|
Digests are unfortunately not exposed on the server-side. This is actually a limitation by React and not Next.js, since react itself takes care of creating a digest and piping the error to the client. I looked into this quite a bit and didn't find any way to pass additional information from the server to the client in the case of an error, e.g. to connect frontend errors with backend ones. |
|
@lforst Do you know how React calculates digest? is there any way to recalculate it from the error object? |
|
I remember I once found it, but it was super convoluted and finding it wasn't easy. Unfortunately, I didn't store the location away so I lost it. I also cannot remember how it was calculated. In any case, it will likely not help us because the hash will break as soon as additional properties are added to the error. |
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
digestto 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
digestvalue?I tried to add a tag in the
beforeSendbut unfortunately thedigestvalue is not available in thebeforeSendhookAll reactions