wraps all the exception, even for network errors, but for us, we want to be able to catch the network issues by ourself, so we can notice the problems. One suggestion is to stop catching all Exceptions, but if it's too much, we would like to at least have the access to the response message, so we can somehow figure out it's a network error or not.
@czhang-hw Starting from version 1.3.2 we now wrap exceptions using a class called AuthyException, you can inspect the cause if you want more detail about the error.
currently, `try { path.append("start"); response = this.post(path.toString(), params);
wraps all the exception, even for network errors, but for us, we want to be able to catch the network issues by ourself, so we can notice the problems. One suggestion is to stop catching all Exceptions, but if it's too much, we would like to at least have the access to the response message, so we can somehow figure out it's a network error or not.