Android以POST请求Web API返回空结果，求问题排查方案

Hey there, let's figure out why your Android POST request to the Web API is returning an empty result. I’ll break down possible issues on both the backend and Android side, along with actionable fixes to get things working.

后端C# Web API排查点 #

1. 标记POST请求特性与路由 #

Your SetHuman method needs explicit annotations to tell Web API it handles POST requests—without this, the API might misroute your Android request and return an empty response:

[HttpPost] // Mandatory: Marks this method as a POST handler
[Route("api/your-controller-name/SetHuman")] // Adjust to match your controller's route
public long SetHuman(HUMAN human)
{
    // Your existing code here
}

Without [HttpPost], Web API defaults to treating the method as a GET endpoint. Android's POST request will fail to find it, leading to empty or 404 results.

2. Fix HUMAN Entity Property Access #

Make sure all properties in your HUMAN class have public getters and setters. Web API can't bind request data to private/readonly properties, leaving your human object empty:

public class HUMAN
{
    public long ID { get; set; }
    public string NAME { get; set; }
    public byte GENDER { get; set; }
    public short USAGE { get; set; }
    // Add public get/set for all other properties
}

If properties are inaccessible, the backend will try to save an empty entity, which might trigger an exception—but your catch block only returns 0, leaving the client in the dark.

3. Add Proper Error Logging #

Your current catch block just returns 0, which hides the root cause (like database connection issues, typos in DbSet names, or validation errors). Add logging to see exactly what's breaking:

catch(Exception e)
{
    // Use a logging framework (NLog, Serilog) or debug output to track errors
    Debug.WriteLine($"SetHuman failed: {e.ToString()}");
    // Optionally throw a clear error for the client
    throw new HttpResponseException(HttpStatusCode.InternalServerError);
}

This way you can see exactly why the insertion is failing instead of guessing.

4. Verify DbSet Name Spelling #

Double-check that db.HUMen is the correct name for your DbSet<HUMAN>. Entity Framework usually pluralizes entity names (e.g., HUMAN → Humans). A typo here will cause the add operation to fail silently (or throw an exception that your catch block hides).

Android Client HttpMadad Tool Class Fixes #

Your postObjectAndGetID code is incomplete, but here are critical fixes for the missing parts:

1. Properly Serialize & Send JSON #

When sending an object via POST, you need to serialize it to JSON and set the correct Content-Type header—otherwise the backend can't parse the request body:

public static Long postObjectAndGetID(Object o, String Api) {
    try {
        // 1. Serialize your object to JSON
        Gson gson = new Gson();
        String jsonBody = gson.toJson(o);
        
        // 2. Configure the POST request
        URL url = new URL(Api);
        HttpURLConnection conn = (HttpURLConnection) url.openConnection();
        conn.setRequestMethod("POST");
        conn.setRequestProperty("Content-Type", "application/json"); // Required!
        conn.setDoOutput(true);
        
        // 3. Write the JSON body to the request
        OutputStream os = conn.getOutputStream();
        os.write(jsonBody.getBytes("UTF-8"));
        os.flush();
        os.close();
        
        // 4. Read the backend's response
        int responseCode = conn.getResponseCode();
        if (responseCode == HttpURLConnection.HTTP_OK) {
            BufferedReader br = new BufferedReader(new InputStreamReader(conn.getInputStream()));
            String result = br.readLine();
            br.close();
            return Long.parseLong(result); // Parse the returned ID
        } else {
            // Handle error responses (e.g., return -1 instead of null)
            return -1L;
        }
    } catch (Exception e) {
        e.printStackTrace();
        // Avoid returning null—handle the exception explicitly
        return null;
    }
}

Without the Content-Type header, the backend will ignore the request body, leading to an empty human object and failed insertion.

2. Check Android Permissions & HTTPS #

Make sure your AndroidManifest.xml includes network permissions:

<uses-permission android:name="android.permission.INTERNET" />
<uses-permission android:name="android.permission.ACCESS_NETWORK_STATE" />

If your API uses HTTPS, ensure your Android app trusts the server's SSL certificate—otherwise the request will fail silently, returning an empty result.

3. Validate the API URL #

Double-check that the Api parameter points to the correct endpoint (e.g., http://your-server-ip:port/api/controller/SetHuman). Typos in the URL or port number will cause the request to fail.

Quick Testing Tip #

First test your Web API directly using Postman or curl to confirm it returns a valid ID when you send a POST request with a HUMAN JSON object. If the backend works, you know the issue is on the Android side.

内容的提问来源于stack exchange，提问作者Alireza Madad