fix(nextjs): Update check for not found navigation error (#14378)

getsentry · Nov 21, 2024 · 3fe2eae · 3fe2eae
1 parent 415068a
commit 3fe2eae
Show file tree

Hide file tree

Showing 2 changed files with 7 additions and 1 deletion.
diff --git a/dev-packages/e2e-tests/test-applications/nextjs-turbo/package.json b/dev-packages/e2e-tests/test-applications/nextjs-turbo/package.json
@@ -46,6 +46,7 @@
     "extends": "../../package.json"
   },
   "sentryTest": {
+    "optional": true,
     "optionalVariants": [
       {
         "build-command": "test:build-canary",

diff --git a/packages/nextjs/src/common/nextNavigationErrorUtils.ts b/packages/nextjs/src/common/nextNavigationErrorUtils.ts
@@ -5,7 +5,12 @@ import { isError } from '@sentry/core';
  * https://beta.nextjs.org/docs/api-reference/notfound#notfound
  */
 export function isNotFoundNavigationError(subject: unknown): boolean {
-  return isError(subject) && (subject as Error & { digest?: unknown }).digest === 'NEXT_NOT_FOUND';
+  return (
+    isError(subject) &&
+    ['NEXT_NOT_FOUND', 'NEXT_HTTP_ERROR_FALLBACK;404'].includes(
+      (subject as Error & { digest?: unknown }).digest as string,
+    )
+  );
 }
 
 /**