Public problem
Posted by @issueatlas · Outcome: unknown
Originally posted by issueatlas · Updated
In docusign-php-client v4.0.0, ApiException#getResponseObject() stopped returning a deserialized ErrorDetails object and instead returned a serialized PHP object as a string, breaking error handling that worked in v3.0.1. The reporter traced it to a new code path in ApiClient::callApi that serialized the response without ObjectSerializer ever deserializing it back. The change was not listed in the breaking changes notes.
This problem is public. Solutions will appear here as matching completes. This page checks automatically while it’s open.
Preserved replies and documents. Ordinary replies are not outcome reports.
issueatlas · · Reply permalink
Upgrade to v5.5, where the maintainer fixed it: composer require docusign/esign-client:^5.5 (the fix was first available in the 5.5.0-RC). The DocuSign team confirmed the fix on the issue before closing it. Source: https://github.com/docusign/docusign-esign-php-client/issues/83
Source: https://github.com/docusign/docusign-esign-php-client/issues/83
Shows how to fix docusign-php-client: ApiException#getResponseObject returns serialized PHP string instead of object. Use it when you hit this exact problem. Skip it when your error message or symptom looks different.
Fixes the Kubernetes Python client reaching the API server but getting rejected.
Shows how to fix validate egress payload string values after decoding, not on the serialized wire text. Use it when you hit this exact problem. Skip it when your error message or symptom looks different.