Thomas Keller

Care to give some implementation hints where to start? I'd try and pick this one up.

Issue is that `AndroidInjector` has a `void inject(T instance);` and therefor does not enforce a specific `void inject(MyApplication instance)` method in the application component (which derives from said interface). `dagger-reflect`...

I don't have another `buildscript` section other than in my root project's `build.gradle` file and face the same problem (build tools 1.5.0). What I found weird though is that `lombok`...

Don't mind me, that only proved that `configurations.classpath.exclude group: 'com.android.tools.external.lombok'`worked as expected x)

@danielgomezrico Still haven't gotten it to work :(

I had the same problem with the most recent version 2.4 - the issue for me was that I had an active emulator in the background and that apparently confused...

I just got notice of https://github.com/square/okhttp/issues/5151 that explains the issue in more detail. Working around with `IOException`s is cool for me, what I dislike however was that I apparently saw...

Also, I was merely bumping dependencies (OkHttp from 4.6.0 to 4.8.1, Retrofit from 2.8.1 to 2.9.0 to get Rx3 support), so with the previous dependencies and Rx2 this issue did...

@YaowenGuo Very good overview, indeed! Now the question is: If any user picks any of the factory methods (`create()`, `createSynchronous()`, `createWithScheduler()`) is he/she aware that this comes at a price...

Also, I think the real culprit is really `okhttp`, look at the implementation of `RealCall.java`: ```java @Override protected void execute() { boolean signalledCallback = false; transmitter.timeoutEnter(); try { Response response...