SyntaxError: Invalid JSON from Internal Server Error in frontend-web
Error
Events
Users2
Error Frequency
Highlights
- level
- error
- trace.id
- 98d66cd5b53e04d93880bae022b5c194
Contexts
User
- id
- 0fd8ab0d-b98b-4521-8061-9827908130da
Runtime
- service
- frontend-web
- mechanism
- span_status
Trace
- trace.id
- 98d66cd5b53e04d93880bae022b5c194
- span.id
- bafa4af0bea57525
- parent_span.id
- 0b8de9082104f0e9
Stack trace
Error message
Unexpected token 'I', "Internal S"... is not valid JSON
SyntaxError: Unexpected token 'I', "Internal S"... is not valid JSONin S"...in app
No source linked for this file.
at JSON.parse (<anonymous>)in JSON.parsein app
No source linked for this file.
at f (http://frontend-proxy:8080/_next/static/chunks/0zzy1y99582vs.js:1:70798):1in app
Loading source…
Raw
SyntaxError: Unexpected token 'I', "Internal S"... is not valid JSON
at JSON.parse (<anonymous>)
at f (http://frontend-proxy:8080/_next/static/chunks/0zzy1y99582vs.js:1:70798)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 'I', "Internal S"... is not valid JSON
- fingerprint
- 6a199c55
- across routes
- 626b83cf
- same shape
- d715e7a4