okhttp3

I'm trying to figure out why sometimes I get this error javax.net.ssl.SSLProtocolException: SSL handshake terminated: ssl=0x60d46c90: Failure in SSL library, usually a protocol error error:1409443E:SSL routines:SSL3_READ_BYTES:tlsv1 alert inappropriate fallback (external/openssl/ssl/s3_pkt.c:1256 0x60d57f40:0x00000003) the code that makes this request: private <T> void send(final String url, final Map<String, String> args, final RequestCallback<T> callback, final Parser<T> pParser, final Context pContext, final HTTP_METHOD method, final Map<String, String> headers, final BODY_TYPE bodyType) {

I want to send a request body like this : How I send this ? I will send it as a class ? "email":{ "emailto":"foo@bar.com", "emailfrom":"foo@bar.com", "emailcc":"foo@bar.com", "emailbcc":"foo@bar.com", "emailsubject":"Subject", "emailtag":"Information", "emailtextbody":"---", "attachments":[] } val formBody = FormBody.Builder() .add("email", "Your message") .build() val request = Request.Builder() .url(url) .post(formBody) .addHeader("_Token","") .addHeader("Content-Type","application/json") .build() I highly suggest to use Retofit for such case, but if you really need to deal with raw Request

I'm experiencing an ExceptionInInitializerError exception on VM running Kitkat 4.4.2 with Multidex enabled. java.lang.ExceptionInInitializerError at okhttp3.OkHttpClient.newSslSocketFactory(OkHttpClient.java:263) at okhttp3.OkHttpClient.<init>(OkHttpClient.java:229) at okhttp3.OkHttpClient$Builder.build(OkHttpClient.java:1015) at myapp.utils.Utils.getHttpClientBuilder(Utils.java:131) at myapp.fragments.FragmentHome.getHome(FragmentHome.java:326) at myapp.fragments.FragmentHome.onViewCreated(FragmentHome.java:135) I have the following libraries: implementation 'jp.wasabeef:recyclerview

OkHttp has recently dropped support for Android 4 , except via a separate 3.12.x branch that will be supported until end of Dec 2020 (and probably receive no more than critical updates or bugfixes). On the assumption that you wish to continue to support Android 4, like I do, since 10% of the Android user base is still a significant proportion, and don't want to be stuck in a dead-end branch... Rather than being stuck on the 3.12.x branch for all sdk versions, is there any way of using the 3.12 branch for sdk < 21 and the 3.13 branch for sdk >= 21 , a bit like it would of course be possible to

I updated our app to use the most recent Android Firebase SDK v11.0.0 ( https://firebase.google.com/support/release-notes/android#20170607 ) and out of the suddenly we bunch of new proguard errors appear, FYI everything was working well before with proguard. Before: compile 'com.google.firebase:firebase-messaging:10.2.6' compile 'com.google.android.gms:play-services-vision:10.2.6' After: compile 'com.google.firebase:firebase-messaging:11.0.0' compile 'com.google.android.gms:play-services-vision:11.0.0' The issue is that it doesn't seem to be a simple new missing proguard entry, but it seems

i am using okHttp 3.2.0 and here is code for building request object MediaType JSON = MediaType.parse(AppConstants.CONTENT_TYPE_VALUE_JSON); RequestBody body = RequestBody.create(JSON, requestBody); HttpUrl url = new HttpUrl.Builder() .scheme("http") .host("192.168.0.104") .port(8080) .addPathSegment("mutterfly-server") .addPathSegment("j_spring_security_check") .addQueryParameter("j_username", jsonObject.getString("emailId")) .addQueryParameter("j_password", jsonObject.getString("password")) .build(); request = new Request.Builder() .addHeader(AppConstants.CONTENT_TYPE_LABEL, AppConstants

I am using Retrofit 1.9 with okhttp 2.4.0. So far we have SPDY protocol disabled on server side (I checked it by this ). And enabled protocol on server side is HTTP/2 (I checked it by this ). So I was thinking that okhttp will try to make an api call using HTTP/2 (latest one protocol) but it's using HTTP/1.1 on android device 4.2.2 samsung S4 - D/Retrofit : OkHttp-Selected-Protocol: http/1.1 Someone told me that android device doesn't support SPDY until 5.0 (I don't have any proof), so that device never attempted to use a SPDY connection. But I am sure that our server not using SPDY at all I