Next.js reuses I/O object on Vercel Edge routes

[lforst]

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.34.0

Framework Version

Next.js 13

Link to Sentry event

No response

SDK Setup

No response

Steps to Reproduce

1. Have auto instrumented Next.js application with Vercel edge routes
2. Send multiple concurrent requests to the edge route

Expected Result

No errors

Actual Result

This invocation reused an I/O object (streams, request/response bodies, and others) created by a previous invocation, which is not permitted.

[lforst]

Looking into this it seems like our transport is reusing fetch promises across different invocations.