28

I have a response coming back from a server and I am expecting a String value, so I wrote this for parsing it

public String getMessageFromServer(JSONObject response) {
    String msg = response.getString("message");
    return msg;
}

then, when I use this in my code and get a null value from the server, the function doesn't return null, it returns "null" instead.

I have seen this bug report, but I don't see a solution.

EDIT:

I have a small hack to solve this but it's ugly and I'm looking for a better solution:

public String getMessageFromServer(JSONObject response) {
    Object msg = response.get("message");
    if(msg == null) {
         return null;
    }
    return (String) msg;
}    

EDIT #2:

after years, going back to this question, I see that I was not entirely wrong here and that JSONObject has a built in method for this.

The way to get an optional value from a JSONObject is with using this method JSONObject.optString("message", DEF_VALUE);

8
  • 1
    it is ok, but it's an ugly hack and I dislike it Commented Oct 29, 2012 at 8:36
  • 1
    Why is that ugly or a hack? You are just doing it well Commented Oct 29, 2012 at 8:37
  • 1
    it's ugly because, I expect a String value (that can be null) but have to deal with type casting. Commented Oct 29, 2012 at 8:40
  • Would checking for "null", in the first example, be less ugly? Commented Oct 29, 2012 at 8:45
  • 1
    @thepoosh - you are optimizing prematurely. It is highly unlikely that the difference between == and String.equals will be significant. Commented Oct 29, 2012 at 9:15

4 Answers 4

28

The hack looks okay for your situation.

The other option would be to use the method boolean isNull(String key) and then based on the returned boolean value proceed with your option. Something like:

public String getMessageFromServer(JSONObject response) {
    return ((response.has("message") && !response.isNull("message"))) ? response.getString("message") : null;
} 

But then, I don't think there's much of a difference between the your current implementation and this.

Sign up to request clarification or add additional context in comments.

2 Comments

+1 for pointing out the correct method to check for a null value. But I don't agree when you say there is not much difference. The isNUll-call is cleaner and should be preferred towards relying on Object and casting.
can't you remove the response.has("message)" check? Whenever that key doesn't exist, isNull will return true, so getString won't be called and no exception will be thrown.
3

This is easy to solve when using Kotlin class extensions:

fun JSONObject.optNullableString(name: String, fallback: String? = null) : String? {
    return if (this.has(name) && !this.isNull(name)) {
        this.getString(name)
    } else {
        fallback
    }
}

Then e.g. name will be null in:

val name : String? = JSONObject("""{"id": "foo", "name":null}""").optNullableString("name")

Comments

0

More simple way in Kotlin

fun JSONObject.getNullableString(name: String) : String? {
    if (has(name) && !isNull(name)) {
        return getString(name)
    }
    return null
}

Comments

0

In android sdk default value in optString method is annotated as @NonNull. Just skip it and simplify to get value or null:

fun JSONObject.optStringOrNull(key: String, fallback: String? = null): String? {
    val obj: Any? = opt(key)
    if (obj is String) {
        return obj
    } else if (obj != null) {
        return obj.toString()
    }
    return fallback
}

Comments

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.