unexpected end of stream on okhttp3.Address@34845fb

Samebug tips1

Either your request in not properly written (check this answer: or you're running into a OkHTTP bug, in which case you should update OkHTTP to 2.4 (or further) and check this discussion: and issues #1517 & #1518

Don't give up yet. Our experts can help. Paste your full stack trace to get a solution.

Solutions on the web7619

  • unexpected end of stream on okhttp3.Address@34845fb
  • via GitHub by lkhore
    , 1 year ago
    unexpected end of stream on okhttp3.Address@34845fb
  • unexpected end of stream on okhttp3.Address@5106fe42
  • Stack trace

    • unexpected end of stream on okhttp3.Address@34845fb at okhttp3.internal.http.Http1xStream.readResponse( at okhttp3.internal.http.Http1xStream.readResponseHeaders( at okhttp3.internal.http.HttpEngine.readNetworkResponse( at okhttp3.internal.http.HttpEngine.access$200( at okhttp3.internal.http.HttpEngine$NetworkInterceptorChain.proceed( at okhttp3.internal.http.HttpEngine.readResponse( at okhttp3.RealCall.getResponse( at okhttp3.RealCall$ApplicationInterceptorChain.proceed( at okhttp3.RealCall.getResponseWithInterceptorChain( at okhttp3.RealCall.access$100( at okhttp3.RealCall$AsyncCall.execute( at at java.util.concurrent.ThreadPoolExecutor.runWorker( at java.util.concurrent.ThreadPoolExecutor$ at Caused by: \n not found: size=0 content=… at okio.RealBufferedSource.readUtf8LineStrict( at okhttp3.internal.http.Http1xStream.readResponse( ... 14 more

    Write tip

    You have a different solution? A short tip here would help you and many other users who saw this issue last week.

    Users with the same issue

    3 times, 1 year ago
    Once, 6 months ago
    4 times, 1 year ago
    4 times, 3 weeks ago
    Unknown user
    Once, 10 months ago
    6 more bugmates