Create a variation of HelloSignException to denote 404s #45

Activity

1. cmpaul

   added

   enhancement

   on Feb 25, 2017
2. cmpaul

   changed the title [-]Create a variation of `HelloSignException` to denote 404s[/-] [+]Create a variation of HelloSignException to denote 404s[/+] on Feb 25, 2017
3. cmpaul

   self-assigned this

   on Feb 27, 2017
4. mashley806 commented on Mar 24, 2017

   

   mashley806

   on Mar 24, 2017

   More actions

   I 2nd this request. It would be great if HelloSign could throw different exceptions for different events. For example, a couple of weeks ago when AWS was down our end users couldn't sign documents and we were just displaying a generic issue occurred prompt. It would be great if HelloSign could throw a HelloSignMaintenanceException which we could catch and show the user a more friendly meaningful message.

   Thanks for your consideration. Matt

   👍React with 👍1Reacted by Chris Paul
5. jspaetzel

   unassigned

   cmpaul

   on Jan 8, 2019
6. Framinus commented on Jan 11, 2019

   

   Framinus

   on Jan 11, 2019

   More actions

   The following exception is thrown for the error message body when a 409 status code is returned:

   Caused by: org.json.JSONException: A JSONObject text must begin with '{' at character 0
   at org.json.JSONTokener.syntaxError(JSONTokener.java:410) ~[hellosign-java-sdk-4.0.9-jar-with-dependencies.jar!/:?]
   at org.json.JSONObject.(JSONObject.java:179) ~[hellosign-java-sdk-4.0.9-jar-with-dependencies.jar!/:?]
   at org.json.JSONObject.(JSONObject.java:402) ~[hellosign-java-sdk-4.0.9-jar-with-dependencies.jar!/:?]
   at com.hellosign.sdk.http.HttpClient.asJson(HttpClient.java:206) ~[hellosign-java-sdk-4.0.9-jar-with-dependencies.jar!/:?]
   at com.hellosign.sdk.HelloSignClient.createEmbeddedRequest(HelloSignClient.java:797) ~[hellosign-java-sdk-4.0.9-jar-with-dependencies.jar!/:?]
7. jtreminio-dropbox

   added

   legacyRelated to legacy, non-OpenAPI SDKRelated to legacy, non-OpenAPI SDK

   on Jun 30, 2022