[BUG] if server respond with 204(no content) client getting NPE here

[zhuravskiy]

Good day!

https://github.com/recurly/recurly-client-java/blob/9fba0d3393496ee6b269131a139ef92d7dd82a4a/src/main/java/com/recurly/v3/BaseClient.java#L147C11-L147C82

if (BINARY_TYPES.contains(contentType.type() + "/" + contentType.subtype())) {

please replace to

if (contentType != null && BINARY_TYPES.contains(contentType.type() + "/" + contentType.subtype())) {

[cheekychops]

Opened #338 with this guard, applied on both dereference sites — the success path reported here, and the error path (if (!response.isSuccessful())), where a null Content-Type currently costs you the status code as well: the NPE replaces the typed exception ExceptionFactory would otherwise produce.

We hit both variants in production on 2–3 August 2026 against 6.2.0. Worth noting for anyone else who lands here: because a NullPointerException is not a RecurlyException, it escapes every catch a caller writes around this SDK, including retry logic keyed on server failures. One of ours was an Idempotency-Key retry, so the replay surfaced as an NPE rather than the original outcome.

#338 includes two BaseClientTest cases that fail with the exact NPE when the guard is reverted.