Is it beneficial to throw a catched IOException as an UncheckedIOException in order to prevent NullPointerException?

Not using UncheckedIOException, NullPointerException possible

public void callerMethod() {     Object result = ioMethod();      // call instance method of result }  public Object ioMethod() {     try {         // IO Stuff         return new Object();     }     catch (IOException e) {         e.printStackTrace();     }      return null; } 

Using UncheckedIOException, NullPointerException not possible

public void callerMethod() {     Object result = ioMethod();      // call instance method of result }  public Object ioMethod() {     try {         // IO Stuff         return new Object();     }     catch (IOException e) {         throw new UncheckedIOException(e);     } } 

In both cases, null is not a valid response type of ioMethod (it would only occur due to an IOException). Should I throw the unchecked exception (UncheckedIOException) early in order to prevent an unchecked exception later (NullPointerException) or not try to prevent the NullPointerException?