I just found out that Kobalt itself uses Okio, and...
# kobalt
s
I just found out that Kobalt itself uses Okio, and it's a different version than the one my project uses (since I use Retrofit v2 and Kobalt uses v1). Could that be interfering? Maybe Kobalt is adding itself to the classpath and so interfering with libraries that it also contains. Not sure if this is actually happening, just a thought.