Many endpoints invoke .execute() in OkHttpJsonApiClient.kt yielding a raw Response. However, in branches where !response.isSuccessful, the network Response is completely ignored and left unclosed. OkHttp strictly demands that responses must be explicitly closed to free socket connections. Repeated failures will aggressively deplete the connection pool and trigger SocketException.
Many endpoints invoke .execute() in OkHttpJsonApiClient.kt yielding a raw Response. However, in branches where !response.isSuccessful, the network Response is completely ignored and left unclosed. OkHttp strictly demands that responses must be explicitly closed to free socket connections. Repeated failures will aggressively deplete the connection pool and trigger SocketException.