Skip to main content
Demo Project

SyntaxError: Invalid JSON Response in frontend-web

Error
Events
Users2
Notify

Error Frequency

Highlights

level
error
trace.id
9cb5b973e7c56efafb951dd3439c8ca8

Contexts

User

id
121743b5-da9a-4744-9ad5-af1dda0d9cd0

Runtime

service
frontend-web
mechanism
span_status

Trace

trace.id
9cb5b973e7c56efafb951dd3439c8ca8
span.id
a9a82073dd90aed6
parent_span.id
f8a973cfe897f652

Stack trace

Error message
Unexpected token 'u', "upstream c"... is not valid JSON
c"...SyntaxError: Unexpected token 'u', "upstream c"... is not valid JSON
JSON.parseat JSON.parse (<anonymous>)
at f (http://frontend-proxy:8080/_next/static/chunks/0zzy1y99582vs.js:1:70798):1
Raw
SyntaxError: Unexpected token 'u', "upstream c"... is not valid JSON
    at JSON.parse (<anonymous>)
    at f (http://frontend-proxy:8080/_next/static/chunks/0zzy1y99582vs.js:1:70798)

Tags

service

frontend-web100%

Event grouping

Events join this issue when their fingerprint matches: the error type, the message with volatile parts (ids, numbers, hex) replaced, the service, the span name, and the in-app frames.

normalized
Unexpected token 'u', "upstream c"... is not valid JSON
fingerprint
2453d0d1
across routes
36b73825
same shape
4c41b620

Trace

Logs

All events

Session replay