In OkHttpResponse#close method (Github link), you do nothing there. But in fact, the response object, which is an OkHttp's Reponse should be closed, as it implements the AutoClosable interface of Java.
We had this message regulary before :
A connection to [Genesys cloud URL here] was leaked. Did you forget to close a response body? To see where this was allocated, set the OkHttpClient logger level to FINE: Logger.getLogger(OkHttpClient.class.getName()).setLevel(Level.FINE);
We did not reproduced it on demand, but it was due to the fact that the response is not closed on the SDK side.
The very moment we used reflection (in our code) to forcefully close the response when the SDK's OkHttpResponse#closemethod is called, the alert was no more seen.
So could you update the SDK's code of this class to transform @Override public void close() throws Exception { }into @Override public void close() throws Exception { response.close(); } please?
#PlatformSDK------------------------------
Gaël BLAISE
National Bank of Canada
------------------------------