This error means the JSON parser reached the end of the input before the data was complete. Common causes are truncated responses, missing brackets or braces, trailing commas, or reading an empty response as JSON. Mehr
What the error means:
The parser expected more JSON (for example, a closing brace, bracket, or another token) but the input ended. In JavaScript this commonly appears as 'Unexpected end of JSON input' thrown by JSON.parse or when response.json() fails.
Common causes:
- Truncated or empty HTTP response body (network error, server sent nothing, or response stream closed early).
- Server returned plaintext, HTML error page, or other non-JSON content.
- Malformed JSON (missing closing brace '}', bracket ']', or missing quotes).
- Trailing commas in objects or arrays (invalid in strict JSON).
- Attempting to parse before all data is available (streaming or asynchronous logic bug).
Debugging checklist:
1) Inspect the raw response: log the response text before parsing (for fetch, use response.text()). That shows whether the body is empty or contains an error page.
2) Validate JSON with an online linter or a local validator to find structural problems.
3) Check server logs to see if the backend errored and returned an incomplete response.
4) Ensure correct Content-Type header (application/json) so clients expect JSON.
5) Look for accidental string concatenation or truncation when building JSON on the server.
6) In environments with streaming, ensure you await the full body and do not call JSON.parse on partial chunks.
Quick fixes and examples:
- If using fetch in frontend: use
const text = await response.text();
console.log(text); // inspect
const data = text ? JSON.parse(text) : null; // guard against empty body
- In Node/Express, ensure you send valid JSON: res.json(obj) instead of res.send(string) with a mistake.
- If the server may return an empty 204 No Content, do not call response.json(); handle 204 specially.
Prevention tips:
- Always produce well-formed JSON from the server; use framework helpers that serialize safely.
- Add defensive parsing on the client: check for empty or non-JSON responses before calling JSON.parse.
- Add unit/integration tests that validate typical and error HTTP responses.
If you share the raw response text or the client/server code snippets, I can point out the exact problem and show a corrected example.
