Jake Wharton

That one doesn't really cover it. I guess there isn't a sample for it. It's a combination of https://github.com/square/retrofit/blob/e6a7cd01657670807bed24f6f4ed56eb59c9c9ab/samples/src/main/java/com/example/retrofit/DeserializeErrorBody.java and https://speakerdeck.com/jakewharton/making-retrofit-work-for-you-droidcon-uk-2016?slide=214

That is not possible because of serialization requirements. On Mon, Aug 28, 2017, 11:40 PM Vasyl Khrystyuk wrote: > Yep. The first sample is good. It is worst then retrofit1...

I don't know what that means On Thu, Sep 7, 2017 at 5:26 AM vidhithakrar wrote: > Any plan to support custom annotation on an interface in 3.x? > >...

I see no use to doing that. What would you use it for? On Thu, Sep 7, 2017 at 1:38 PM vidhithakrar wrote: > @zergtmn Yeah, something like that. One...

OkHttp will interrupt the thread itself if you are using blocking requests. Can you express the problem in some kind of test case or sample that I can run? I'm...

Can you provide a self-contained sample which reproduces the problem? We have plenty of usage of `.execute()` in Retrofit's own test suite without issue.

If something changed solely with an AGP version change then it's like a result of a newer version of R8. The easiest way for me to look at the problem...

Thank you for the excellent repro. I don't think there's any way to mitigate this from Retrofit's side with a simple keep rule. On Cash App we actually wrote an...

When running R8 in full mode all generic types are removed unless they are explicitly kept. Retrofit automatically keeps the generic part for users of `Call`, but if you are...

Those rules are painful. It bloats the APK since those types are likely widespread in your application. Not sure we can safely remove them at this point–even with the processor.