Identifying the errors

It's a bad idea to silently ignore exceptions like this.  Imagine an exception was thrown, this would ignore it and return null - probably causing a NullPointerException somewhere else - and it would be hard to figure out why.

Instead of "return null;" use "throw new RuntimeException(e);".  Now, if a JSONException occurs it will get thrown and an error will explain what the problem is and where.

See [this explanation](http://stackoverflow.com/a/921583/16050) for more detail on why silently catching exceptions is a bad idea.