fix: capturing parent exception JsonException

[sbansla]

• Fix when API returns null for integer fields (e.g., "code": null) in error responses.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
100.0% Duplication on New Code

See analysis details on SonarQube Cloud

[Copilot]

Pull request overview

This PR hardens error-response deserialization in Twilio REST clients so that malformed/unexpected JSON (including cases like integer fields returned as null) doesn’t escape as an unhandled JSON parsing/serialization exception, and instead falls back to existing error handling.

Changes:

• Broadened exception handling during RestException.FromJson(...) parsing from JsonReaderException to JsonException.
• Broadened exception handling during RestApiStandardException.FromJson(...) parsing from JsonReaderException to JsonException.
• Applied the same behavior consistently across the standard, no-auth, and orgs-token REST clients.

Reviewed changes

Copilot reviewed 3 out of 3 changed files in this pull request and generated no comments.

File	Description
src/Twilio/Clients/TwilioRestClient.cs	Catch JsonException during error payload parsing to prevent unhandled JSON exceptions and allow fallback behavior.
src/Twilio/Clients/NoAuth/TwilioNoAuthRestClient.cs	Same broadened JSON exception handling for the no-auth client error parsing path.
src/Twilio/Clients/BearerToken/TwilioOrgsTokenRestClient.cs	Same broadened JSON exception handling for the bearer-token orgs client error parsing path.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.