Hacktoberfest 2026: as issues que os mantenedores marcaram para outubro, abertas e boas para iniciantes. Ver issues do Hacktoberfest

Using `@sentry/nextjs` and `@sentry/cloudflare` together crashes every request with `context.getValue is not a function`

Fechada
  • Algo errado?
#24,603 3 comentários 0 reações 1 responsável Ver no GitHub

Mantenedores costumam responder em até 1 dia

@ihsraham já está trabalhando nisso.

Desde 24/9/2026.

Avaliação

Dificuldade
4/5
Tempo estimado
3-5 dias
Facilidade para iniciantes
48/100
Tipo de issue
Bug
Clareza
Claramente especificada
Status de atividade
Ativa
Stack de tecnologia
nextjs, typescript
Domínio
observability

Direção de pesquisa

Start with packages/server-utils/src/async-context.ts and packages/opentelemetry/src/asyncContextStrategy.ts, comparing how each strategy discovers and reuses AsyncLocalStorage. Run both reproduction snippets and verify that mismatched stores no longer cause getCurrentScope or trace.getSpan to crash; the unsupported combined SDK behavior should remain explicit.

Escrita pelo modelo de indexação a partir do texto da issue.

Descrição

Bug Cloudflare Workers Next.js
Description

A Next.js app on Cloudflare Workers that initializes @sentry/nextjs in instrumentation.ts and also wraps the Worker entry with @sentry/cloudflare's withSentry fails on every request:

TypeError: e.getValue is not a function
    at getScopesFromContext
    at getScopes
    ...
    at _onSpanEnded
    at end

Seen with @sentry/[email protected] and @sentry/[email protected], which share the same @sentry/core.

Root cause

The two SDKs install different async context strategies, and the second one reuses the AsyncLocalStorage of the first even though the two strategies put different things into it:

Strategy Installed by ALS store
setAsyncLocalStorageAsyncContextStrategy (packages/server-utils/src/async-context.ts) @sentry/cloudflare (withSentry) { scope, isolationScope }
setOpenTelemetryContextAsyncContextStrategy (packages/opentelemetry/src/asyncContextStrategy.ts) @sentry/nextjs edge build (via @sentry/vercel-edge) an OpenTelemetry Context, also read by the global context manager it registers

Both pick up an existing store like this, without checking which strategy created it (added in #22889):

const existing = getAsyncContextStrategy(getMainCarrier()).getTracingChannelBinding?.()?.asyncLocalStorage;
const asyncLocalStorage = existing ?? new AsyncLocalStorage();

Once the stores are shared, api.context.active() returns the plain { scope, isolationScope } object, and getScopesFromContext(ctx) (or trace.getSpan(ctx)) calls ctx.getValue() on it. It fails in both install orders.

Reproduction

No framework needed:

import { getCurrentScope, withIsolationScope } from '@sentry/core';
import { setAsyncLocalStorageAsyncContextStrategy } from '@sentry/cloudflare';
import { setOpenTelemetryContextAsyncContextStrategy } from '@sentry/opentelemetry';

setAsyncLocalStorageAsyncContextStrategy();
withIsolationScope(() => {
  setOpenTelemetryContextAsyncContextStrategy();
  getCurrentScope(); // TypeError: context.getValue is not a function
});

The reverse order fails the same way:

import { context, trace } from '@opentelemetry/api';

setOpenTelemetryContextAsyncContextStrategy();
setAsyncLocalStorageAsyncContextStrategy();
withIsolationScope(() => {
  trace.getSpan(context.active()); // TypeError: context.getValue is not a function
});
Expected

A strategy only reuses an AsyncLocalStorage that holds the store shape it expects, for example by tagging the binding with its store type and creating a fresh ALS on a mismatch.

This only stops the crash. Two SDKs in one runtime still end up with one active strategy and one current client, so combining @sentry/nextjs and @sentry/cloudflare stays unsupported. It would still be better to fail soft than to break every request. The same clash can happen with any other pair of SDKs that use different strategies.

Linguagem predominante
TypeScript
Estrelas
8.8k
Forks
1.9k
Merge médio
1d 10h
PRs com merge (30d)
562

Preparar o ambiente

Primeiros passos

  1. Leia a issue inteira e depois o guia de contribuição do projeto.
  2. Comente na issue dizendo que vai assumir — evita que duas pessoas façam o mesmo trabalho.
  3. Faça um fork do repositório e trabalhe em uma branch.
  4. Abra um pull request que referencie o número da issue.

Mais de getsentry/sentry-javascript

Todas as issues de getsentry/sentry-javascript

Issues semelhantes

Mais issues de TypeScript

Receba novas issues na sua caixa de entrada

Um resumo curto de issues do GitHub para quem está começando.