Leaking connections?
DaveSanders opened this issue · comments
I'm noticing these in my console on occasion:
W/OkHttpClient: A connection to http://10.0.2.2:3000/ was leaked. Did you forget to close a response body?
Looks like there might need to be some error handling around the OKHttp calls:
Or is this something I'm doing wrong with wasp? As far as I know, I'm making standard gets and my usage is pretty basic.