Java Helper Library 13.0.0: Handle unknown fields in nested API responses
Java Helper Library 13.0.0 fixes a critical issue where versions 10.0.0-12.1.1 crash on unknown fields in nested API responses, now matching the behavior of other Twilio Helper Libraries. Upgrade immediately to prevent integration failures when Twilio adds new optional API fields.
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.
Source: original entry ↗
More from Twilio
Follow Twilio to get its new changes in your feed and email digest.
Voice Integrity now supports all three major US networks
Voice Integrity, part of Twilio's Voice Trust offering, now supports all three major US carrier networks. Businesses can register their details and outbound phone numbers directly with carriers to help identify legitimate traffic and reduce spam blocking.
Unified Login for SendGrid Marketplace Customers
SendGrid marketplace customers can now create individual Twilio logins for each user, enabling granular permission management instead of shared admin access. This rollout applies to all marketplace integrations including Azure, Google Cloud, Heroku, and AWS.
Webhook Configuration API is now Generally Available
The Webhook Configuration API enables customers to configure authentication and delivery settings for outbound webhooks on a per-URL basis through Webhook Settings and Webhook Rules resources.