sentry-javascript: [@sentry/nextjs] Errored API routes trigger "API resolved without sending a response"

Please do not close

Please don’t close - this is still an issue that should be resolved

I’m still seeing the messages on 7.24.2, I have removed all of my withSentry wrappers and I never added the externalResolver change.

Why is this error closed? With the last version I still see the error, there is a warning but the problem is still there.

Any plan on this one? I’m currently doing something like this to get rid of the message

import * as Sentry from '@sentry/nextjs';

// ISSUE: https://github.com/getsentry/sentry-javascript/issues/3852
// API resolved without sending a response for *, this may result in stalled requests.
const withSentry = (fn) => async (req, res) => {
  await Sentry.withSentry(fn)(req, res);
  await res.end();
};

export default withSentry;

You can set externalResolver to true in api route config since it is handled by sentry (external) https://nextjs.org/docs/api-routes/api-middlewares#custom-config

We ever fixing this or what? Annoying to have logs spammed.

It does this for all my requests as well, even though I do this:

return res.status(200).json({ success: true });

I hope this will be fixed 😃

I can confirm this is an issue on 7.32.1 but the same pattern was working fine on 7.31.1.

I didn’t see anything in the diff which would indicate the breaking change, but the constant logging has definitely returned. Downgrading to 7.31.1 resolves again.

Resolved by https://github.com/getsentry/sentry-javascript/pull/5778, which is published with 7.14.0.

It seems like the SENTRY_IGNORE_API_RESOLUTION_ERROR environment variable is not being respected anymore either. This is especially ironic since we also added the externalResolver API prop on every handler, so we get no logging from NextJS but we get Sentry’s warning that NextJS might log for every request. Is that variable still working for anyone?

Edit: I don’t even see anything in the repo that’d be looking for such a variable, but maybe it’s buried in the CLI itself? In my case it’s being provided in next.config.js alongside other env variables such as SENTRY_URL, SENTRY_PROJECT, etc, and all of those are working fine.

Why is this error closed?

Because it was fixed… in a way which turned out to break other things, and had to be reverted. I’ll reopen.

As for finding a new solution, I’m open to ideas. We’ve been focusing on trying to ship our next major version, so I haven’t been able to dive back into this at a deep level, but I will admit that even coming up with my turned-out-to-cause-other-problems hack took quite a bit of poking and prodding and digging through not only nextjs source code but node source code as well, and so I don’t expect finding a new approach is going to be a trivial problem.

In the meantime, you can suppress next’s warning yourself by using the “external resolver” option in your API route (docs here). I’ve also just pushed https://github.com/getsentry/sentry-javascript/pull/4706, to allow our warning to be suppressed as well.

@kaykdm Thanks for this workaround! Is there a way to set a default config for all API routes ? From the docs it seems that there is no option to do this in next.config.js, which means this config has to be added to all API routes individually.

@KieraDOG the workaround in this comment did not work for me. This resulted in the response being ended before the actual content is sent, which means stalling requests (especially in a development environment).