Debugging: truncated error messages, exception handling about avatax-rest-v2-php-sdk HOT 5 CLOSED

An underlying issue is that Guzzle throws a RequestException which the documentation does not show anywhere and naturally truncates data after 120 characters. This means any data AvaTax sends after 120 characters is useless to the developers.

Furthermore, setting catch exceptions to false almost always sends the same stack trace that points to RequestException.php line 113 because Guzzle is reading the HTTP error codes. If you want the AvaTax error to match their documentation, you will need to catch the exception and return the response body similar to this:

if ($exception instanceof \GuzzleHttp\Exception\RequestException) {
    $body = $exception->getResponse()->getBody();
    $errorInfo = json_decode($body->read($body->getSize()));
}

Edit: fixed formatting and had json_decode return an object to match Avalara\ErrorInfo

from avatax-rest-v2-php-sdk.

I believe you can set the client to not catch exceptions and actually throw them:

$client = new AvaTaxClient(...);
$client->withCatchExceptions(false);

from avatax-rest-v2-php-sdk.

I believe you can get the full exception response string just by casting the body to a string.

$errorMessage = (string)$throwable->getResponse()->getBody();

from avatax-rest-v2-php-sdk.

Yep, this is correct, the StreamInterface has a __toString method defined but one thing to note is PHP does not allow throwing an exception while casting to a string so if there was some underlying throwable, you will get an empty string back rather than the throwable which could make it harder to debug.

from avatax-rest-v2-php-sdk.

This issue is fixed as part of #183. Please verify and revert if in case it is not resolved at your end.

from avatax-rest-v2-php-sdk.