okhttp 3.8.0: ProGuard "can't find referenced class javax.annotation.Nullable"

According to the 3.8.0 CHANGELOG: “We’ve added a compile-time dependency on the JSR 305 annotations. This is a provided dependency and does not need to be included in your build configuration…”

However, ProGuard brings a lot of messages like this:

okhttp3.Address: can't find referenced class javax.annotation.Nullable
…

This can be worked around by adding jsr305 to the gradle configuration:

    compile 'com.google.code.findbugs:jsr305:3.0.2'

However, according to the docs, this should be done by okhttp dependencies.

[vanniktech]

Have a look at - https://github.com/square/okhttp/pull/3354

[JakeWharton]

That is not OkHttp’s package and so those rules are effectively useless (aside from dropping warnings in Okio and for JSR 305 annotations). Even if it was OkHttp’s correct package, you’re better off turning off ProGuard than doing such an overly-keepy rule.

On Thu, Oct 26, 2017 at 4:22 PM attaullahpro [e-mail] wrote:

it looks like minifyEnabled is set to true in your build.gradle so it is applying proguard rules. so you should add this rules to your proguard-rules.pro file

-dontwarn okio.** -dontwarn com.squareup.okhttp3.** -keep class com.squareup.okhttp3.** { ; } -keep interface com.squareup.okhttp3.* { *; } -dontwarn javax.annotation.Nullable -dontwarn javax.annotation.ParametersAreNonnullByDefault

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/square/okhttp/issues/3355#issuecomment-339720798, or mute the thread https://github.com/notifications/unsubscribe-auth/AAEEEdEAc1uIR4V-lOVyHFNstfmQCzsKks5swLG2gaJpZM4NaVjH .