`next export` fails when having `_error` and `404` page #6088

bas080 · 2022-10-29T19:59:08Z

Is there an existing issue for this?

I have checked for existing issues https://github.com/getsentry/sentry-javascript/issues
I have reviewed the documentation https://docs.sentry.io/
I am using the latest SDK release https://github.com/getsentry/sentry-javascript/releases

How do you use Sentry?

Sentry Saas (sentry.io)

Which package are you using?

@sentry/nextjs

SDK Version

7.17.2

Framework Version

13.0.0

Link to Sentry event

No response

Steps to Reproduce

Versions

jq .version  < ./node_modules/next/package.json
jq .version  < ./node_modules/@sentry/nextjs/package.json

"13.0.0"
"7.17.2"

Reproduce

npm run build && npm run export


> localu@0.0.1 build
> next build

warn  - You have enabled experimental feature (cpus) in next.config.mjs.
warn  - Experimental features are not covered by semver, and may cause unexpected or broken application behavior. Use at your own risk.

info  - Linting and checking validity of types...
info  - Creating an optimized production build...
info  - Compiled successfully
info  - Collecting page data...
info  - Generating static pages (0/53)
info  - Generating static pages (13/53)
info  - Generating static pages (26/53)
info  - Generating static pages (39/53)
info  - Generating static pages (53/53)
info  - Finalizing page optimization...

Route (pages)                                         Size     First Load JS
┌   /_app                                             0 B             109 kB
├ ● /[language]/[webpage] (ISR: 1 Seconds) (8775 ms)  13.7 kB         128 kB
├   ├ /ru/404 (334 ms)
├   ├ /en/index
├   ├ /he/index
├   ├ /ru/index
├   ├ /en/boat-hire
├   ├ /he/boat-hire
├   ├ /ru/boat-hire
├   └ [+44 more paths]
├ λ /404                                              438 B           109 kB
├ λ /api/[sheet]/[gid]/invalidate                     0 B             109 kB
├ λ /api/[sheet]/[gid]/json                           0 B             109 kB
├ λ /api/email/[language]/[webpage]                   0 B             109 kB
├ λ /api/email/[language]/[webpage]/send              0 B             109 kB
├ λ /api/form/[language]/[webpage]                    0 B             109 kB
├ λ /api/ping                                         0 B             109 kB
├ λ /api/publish                                      0 B             109 kB
├ ● /public/robots.txt                                541 B           115 kB
└ ● /public/sitemap.xml (2449 ms)                     543 B           115 kB
+ First Load JS shared by all                         114 kB
  ├ chunks/framework-3b5a00d5d7e8d93b.js              45.4 kB
  ├ chunks/main-109639d04b48b523.js                   29.4 kB
  ├ chunks/pages/_app-8141b332980f9e18.js             32.1 kB
  ├ chunks/webpack-32ca610b9890a2c4.js                1.81 kB
  └ css/77ad3477c6267d74.css                          5.55 kB

λ  (Server)  server-side renders at runtime (uses getInitialProps or getServerSideProps)
●  (SSG)     automatically generated as static HTML + JSON (uses getStaticProps)
   (ISR)     incremental static regeneration (uses revalidate in getStaticProps)


> localu@0.0.1 export
> next export --threads 1

warn  - You have enabled experimental feature (cpus) in next.config.mjs.
warn  - Experimental features are not covered by semver, and may cause unexpected or broken application behavior. Use at your own risk.

info  - using build directory: /home/ant/projects/localu/.next
warn  - rewrites, redirects, and headers are not applied when exporting your application, detected (rewrites, redirects). See more info here: https://nextjs.org/docs/messages/export-no-custom-routes
info  - Copying "static build" directory
info  - No "exportPathMap" found in "/home/ant/projects/localu/next.config.mjs". Generating map from "./pages"
info  - Launching 1 workers
warn  - Statically exporting a Next.js application via `next export` disables API routes.
This command is meant for static-only hosts, and is not necessary to make your application static.
Pages in your application without server-side data dependencies will be automatically statically exported by `next build`, including pages powered by `getStaticProps`.
Learn more: https://nextjs.org/docs/messages/api-routes-static-export
info  - Exporting (0/4)
info  - Copying "public" directory
info  - Exporting (1/4)
info  - Exporting (2/4)
warn  - Detected getInitialProps on page '/_error' while running "next export". It's recommended to use getStaticProps which has a more correct behavior for static exporting.
Read more: https://nextjs.org/docs/messages/get-initial-props-export

Error occurred prerendering page "/404". Read more: https://nextjs.org/docs/messages/prerender-error
TypeError: Cannot read properties of undefined (reading '__sentry_original__')
    at Object.autoEndTransactionOnResponseEnd (/home/ant/projects/localu/node_modules/@sentry/nextjs/cjs/config/wrappers/utils/responseEnd.js:34:19)
    at /home/ant/projects/localu/node_modules/@sentry/nextjs/cjs/config/wrappers/wrapperUtils.js:92:19
    at bound (node:domain:433:15)
    at runBound (node:domain:444:12)
    at Object.callTracedServerSideDataFetcher (/home/ant/projects/localu/node_modules/@sentry/nextjs/cjs/config/wrappers/wrapperUtils.js:128:5)
    at Function.getInitialProps (/home/ant/projects/localu/node_modules/@sentry/nextjs/cjs/config/wrappers/withSentryServerSideErrorGetInitialProps.js:38:23)
    at /home/ant/projects/localu/node_modules/next/dist/shared/lib/utils.js:84:33
    at Generator.next (<anonymous>)
    at asyncGeneratorStep (/home/ant/projects/localu/node_modules/@swc/helpers/lib/_async_to_generator.js:23:28)
    at _next (/home/ant/projects/localu/node_modules/@swc/helpers/lib/_async_to_generator.js:12:17)
info  - Exporting (3/4)
warn  - Detected getInitialProps on page '/_error' while running "next export". It's recommended to use getStaticProps which has a more correct behavior for static exporting.
Read more: https://nextjs.org/docs/messages/get-initial-props-export

Error occurred prerendering page "/404.html". Read more: https://nextjs.org/docs/messages/prerender-error
TypeError: Cannot read properties of undefined (reading '__sentry_original__')
    at Object.autoEndTransactionOnResponseEnd (/home/ant/projects/localu/node_modules/@sentry/nextjs/cjs/config/wrappers/utils/responseEnd.js:34:19)
    at /home/ant/projects/localu/node_modules/@sentry/nextjs/cjs/config/wrappers/wrapperUtils.js:92:19
    at bound (node:domain:433:15)
    at runBound (node:domain:444:12)
    at Object.callTracedServerSideDataFetcher (/home/ant/projects/localu/node_modules/@sentry/nextjs/cjs/config/wrappers/wrapperUtils.js:128:5)
    at Function.getInitialProps (/home/ant/projects/localu/node_modules/@sentry/nextjs/cjs/config/wrappers/withSentryServerSideErrorGetInitialProps.js:38:23)
    at /home/ant/projects/localu/node_modules/next/dist/shared/lib/utils.js:84:33
    at Generator.next (<anonymous>)
    at asyncGeneratorStep (/home/ant/projects/localu/node_modules/@swc/helpers/lib/_async_to_generator.js:23:28)
    at _next (/home/ant/projects/localu/node_modules/@swc/helpers/lib/_async_to_generator.js:12:17)
info  - Exporting (4/4)
Error: Export encountered errors on following paths:
	/_error: /404
	/_error: /404.html
    at /home/ant/projects/localu/node_modules/next/dist/export/index.js:405:19
    at async Span.traceAsyncFn (/home/ant/projects/localu/node_modules/next/dist/trace/trace.js:79:20)

Notice that the export fails.

Expected Result

That all pages are built

Actual Result

It errors for the _error page.

The text was updated successfully, but these errors were encountered:

bas080 · 2022-10-29T20:26:28Z

I get the same error with nextjs version "12.3.1"

bas080 · 2022-10-29T20:28:22Z

Last version of sentry/nextjs that I used and worked was "7.13.0".

lforst · 2022-10-31T09:07:16Z

Hi, thanks for reporting this!

I was able to reproduce this by running next build && next export while having a _error.js page alongside a 404.js page with our auto wrapping enabled.

For now, you can disable our auto instrumentation to get around the error when exporting by setting autoInstrumentServerFunctions: false.

Nonetheless, we should fix this so I am backlogging this.

lforst · 2023-01-10T15:10:14Z

Hi, this should be fixed in release 7.30.0 of the SDK.

mzruiz · 2023-03-26T18:36:53Z

Commenting so others can see this thread - took a few hours on Google to find.

I was using

  next: "13.2.0",
  react: "18.2.0",

and was receiving Cannot read properties of undefined (reading 'getInitialProps') after running yarn run build.

This issue in the nextjs repo was the closest issue I found to describe what was happening to me.

Ultimately, the recommendation above by @lforst solved it for me.

bas080 added the Type: Bug label Oct 29, 2022

getsantry bot added the Status: Untriaged label Oct 29, 2022

lforst added Package: nextjs Status: Backlog and removed Status: Untriaged labels Oct 31, 2022

lforst changed the title ~~Export fails when using newer version of sentry/nextjs~~ next export fails when having _error and 404 page Oct 31, 2022

hyesungoh mentioned this issue Nov 4, 2022

Attach sentry depromeet/ahmatda-web#12

Merged

This was referenced Jan 3, 2023

@sentry/nextjs failing when exporting static version of nextjs application #6638

Closed

fix(nextjs): Don't write to res.end to fix next export #6682

Merged

lforst self-assigned this Jan 9, 2023

lforst closed this as completed in #6682 Jan 9, 2023

mattkrco mentioned this issue Aug 23, 2023

Error logging not working when using Nextjs with SSG #8862

Closed

3 tasks

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

`next export` fails when having `_error` and `404` page #6088

`next export` fails when having `_error` and `404` page #6088

bas080 commented Oct 29, 2022 •

edited

bas080 commented Oct 29, 2022

bas080 commented Oct 29, 2022 •

edited

lforst commented Oct 31, 2022

lforst commented Jan 10, 2023

mzruiz commented Mar 26, 2023

next export fails when having _error and 404 page #6088

next export fails when having _error and 404 page #6088

Comments

bas080 commented Oct 29, 2022 • edited

Is there an existing issue for this?

How do you use Sentry?

Which package are you using?

SDK Version

Framework Version

Link to Sentry event

Steps to Reproduce

Versions

Reproduce

Expected Result

Actual Result

bas080 commented Oct 29, 2022

bas080 commented Oct 29, 2022 • edited

lforst commented Oct 31, 2022

lforst commented Jan 10, 2023

mzruiz commented Mar 26, 2023

`next export` fails when having `_error` and `404` page #6088

`next export` fails when having `_error` and `404` page #6088

bas080 commented Oct 29, 2022 •

edited

bas080 commented Oct 29, 2022 •

edited