I ran into the same problem and tracked it down to my proguard configuration. It looks like the profiler is using reflection to invoke some of the okhttp3 methods, but they have been separated by proguard.
Adding the following line to my proguard rules solved the problem for me:
-keep class okhttp3.Headers { *; }
source
share