Original question: OkHttp, is there a way to not rely on a connection pool? Hey OkHttp users and/or contributors! Is there a way to use an OkHttpClient withou
I am using Picasso 2.5.2 to use it with OkHttp 2.5.0 The code in onCreate() is like below: File mypath = new File(getFilesDir().getAbsolutePath()+"/"+ date +
When I make a get request to an API, over and over again I see that every request the memory goes up and up until 1gb of ram usage. closing the response and au
I'm using the OkHttp library in my android app to make web requests to a weather API. I've already implemented my code and I'm getting a FATAL EXCEPTION when do
I'm trying to deploy my App on another phone. I already installed the cert on the new phone and I'm still facing this problem. java.security.cert.CertPathValida
I have created below module in my android application. val appNetworkModule = module { // Dependency: OkHttpClient single { var okHttpClient=OkHttpClient.Bu
I have added a new jar file as a module and faced with the above issue. I have already implemented okHttp in my apps gradle file. Seems like the jar file also i
I read some examples which are posting jsons to the server. some one says : OkHttp is an implementation of the HttpUrlConnection interface provided by Ja
I'm creating a secured websocket connection between my server using okhttp library. But my websocket connections keep getting closed after 3 minutes. So I added
I'm working for a customer who has a server with self-signed SSL cert. I'm using Retrofit + CustomClient using wrapped OkHttp client: RestAdapter restAdapter
i followed this tutorial: https://www.journaldev.com/13629/okhttp-android-example-tutorial But when i try to start the project give me this error: Execution fai