Connection leak error

I am using the Java SDK for implementing reset password functionality.
Everything seems to be working fine, but I am getting this error on the back end

 [java] Dec 29, 2017 10:59:32 AM okhttp3.internal.platform.Platform log
 [java] WARNING: A connection to https://(my-domain)/ 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);

Is this error due to some flaw in my code or is it some internal error at auth0 SDK?

I’m assuming that you’re calling the resetPassword method; if that’s the case then your situation seems to be the same as the one reported in this GH issue. A fix was merged only two days ago so there is not yet any release with that change, however, it should be addressed by next release.

Thanks @jmangelo,

Will I have to update the jars or it will be fixed automatically?

Your application will need to use the new (future) release that’s for sure, but to be honest don’t have enough knowledge on Java building pipeline to know how that works as in if it will pick the latest available at each build time or if you need to do something manually. Ideally, production builds in general should not automatically pick new versions as that might mean breaking changes even if unintentional, but I guess the answer is it depends on your setup.

Okay, so is there a way to check on when this fix will be available for use.
So that I can update my code base to incorporate it.