Rob Schilder
02/25/2023, 6:06 PM"@sentry/nextjs": "7.31.1"
and "supertokens-node": "^13.0.2"
, I realised that the API routes were giving a 500, with the following message:
2023-02-25T17:38:56.455Z c7afa71e-b4f9-4cad-971c-e1145720392c ERROR Uncaught Exception {"errorType":"Error","errorMessage":"write after end","trace":["Error [ERR_STREAM_WRITE_AFTER_END]: write after end"," at new NodeError (node:internal/errors:387:5)"," at ServerResponse.end (node:_http_outgoing:968:15)"," at ServerResponse.apiRes.end (/var/task/node_modules/next/dist/server/api-utils/node.js:356:25)"," at ServerResponse.res.end (/var/task/node_modules/@sentry/nextjs/cjs/server/wrapApiHandlerWithSentry.js:152:26)"," at processTicksAndRejections (node:internal/process/task_queues:96:5)"]}
Unknown application error occurred
Runtime.Unknown
The solution now is to temporarily disable the automatic instrumentation of API route handlers and server-side data fetching functions by setting the autoInstrumentServerFunctions
to false.
const moduleExports = {
sentry: {
autoInstrumentServerFunctions: false,
},
};
Now it's still possible to to only wrap specific API route handlers or data fetching functions instead. For API routes, they use the wrapApiHandlerWithSentry
function. But ideally we would want Sentry to work with Supertokens out of the box. Have you guys looked into this already?rp
02/25/2023, 7:15 PMRob Schilder
02/25/2023, 7:32 PMrp
02/25/2023, 7:32 PM