Android注册页连接SQL数据库时JSONException异常的解决方法

Hey there, let’s work through this JSON parsing error you’re facing when connecting your Android registration page to your SQL backend. This error almost always boils down to one thing: the response your app is getting from your server isn’t a valid JSON object—here’s how to fix it step by step:

1. First, check what your backend is actually returning #

Grab a tool like Postman, or just paste your URL_FOR_REGISTRATION into a browser, and look at the raw response. Chances are:

• Your backend is returning plain text (like "Registration successful" or "Email already exists") instead of a structured JSON object.
• Or, it’s returning an HTML error page (like a 500 Internal Server Error page) if something’s wrong with your SQL query or server setup.

Neither of these are valid JSON, so when your code tries to convert them to a JSONObject, it throws that exception. Fix this by updating your backend to return standard JSON, e.g.:

{"status": "success", "message": "Registration completed"}

Or, if you can’t modify the backend, adjust your Android code to handle plain text responses instead.

2. Debug your response handling code #

Take a look at how you’re reading the server response in your RegistrationActivity. Common mistakes here include:

• Trying to parse the response without checking the HTTP status code first. If the server returns a 400/500 error, the response body is probably an error message string, not JSON.
• Not reading the full response correctly, leading to truncated or garbled text that breaks JSON parsing.

Add a log statement to print the raw response string before parsing—it’ll show you exactly what you’re dealing with:

// After fetching the response string
Log.d(TAG, "Raw server response: " + responseString);

3. Handle non-JSON responses gracefully #

Update your parsing logic to check if the response is actually valid JSON before trying to convert it. Here’s a quick example:

try {
    // Check if the response starts with a JSON object/array bracket
    if (responseString.trim().startsWith("{") || responseString.trim().startsWith("[")) {
        JSONObject jsonResponse = new JSONObject(responseString);
        // Process your JSON data here (e.g., check status, show success message)
        String status = jsonResponse.getString("status");
        if ("success".equals(status)) {
            Toast.makeText(this, "Registration successful!", Toast.LENGTH_SHORT).show();
            finish();
        } else {
            String errorMsg = jsonResponse.getString("message");
            Toast.makeText(this, errorMsg, Toast.LENGTH_SHORT).show();
        }
    } else {
        // Handle plain text responses
        Toast.makeText(this, responseString, Toast.LENGTH_SHORT).show();
    }
} catch (JSONException e) {
    Log.e(TAG, "Failed to parse JSON", e);
    Toast.makeText(this, "Registration failed: Server returned invalid data", Toast.LENGTH_SHORT).show();
}

4. Check for character encoding issues #

Sometimes, if your server uses a non-UTF-8 encoding for responses, the string you read might have hidden characters or garbled text that breaks JSON parsing. Make sure you specify UTF-8 when reading the input stream:

// Example with HttpURLConnection
BufferedReader reader = new BufferedReader(
    new InputStreamReader(connection.getInputStream(), "UTF-8")
);

By following these steps, you’ll quickly identify whether the issue is on the backend (invalid JSON output) or frontend (incorrect response handling) and fix it accordingly.

内容的提问来源于stack exchange，提问作者Mohammed Abdeen