Critical fix: Java Helper Library 13.0.0: fixes crash on unknown fields in nested API responses

The Java Helper Library now handles unknown fields gracefully in nested response objects, but if customers are on an affected version, their integration is at risk until they upgrade.

Versions 10.0.0 through 12.1.1 parse nested response types (profile, configuration, webhook, and others) with strict deserialization. When an API response comes back with a field the SDK doesn't recognize, the request fails with ApiConnectionException: Unable to deserialize response: Unrecognized field. Because Twilio APIs can add new optional fields at any time, this is a latent break. Customers’ integrations work today and can start failing without warning the moment a new field ships.

In 13.0.0, the Java Helper Library ignores unknown fields in all response objects, matching how every other Twilio Helper Library already behaves.

What to do

Upgrade to Java Helper Library 13.0.0 or later as soon as possible. Version 13 does include breaking changes so follow the upgrade guide to migrate safely. Once customers are on 13.0.0, their integration handles new optional fields in API responses without hitting deserialization errors.

The Python, Node.js, C#, Ruby, PHP, and Go Helper Libraries are not affected. They already handle unknown response fields the same way.