Parse Kotlin metadata manually to honor nullability and avoid kotlin-metadata-jvm dep

Version: 2.6.0-SNAPSHOT Exception: KotlinNullPointerException Message: Response from {path to my suspend fun…} was null but response body type was declared as non-null

The current structure of my suspend fun in my service interface:

@POST("api/...")
suspend fun request(@Body body: Body): Response?

I’m using Gson for serialization.

Is there a way to declare the response body type as nullable that I’m missing? I’ve tried adding null safety on my response object with ? and @Nullable with no success.

[claucookie]

Just in case it helps. I was experiencing the exact same KotlinNPE issue over the last 2 days and after trying Converters and Adapters what really worked was to return Response<Unit> in the retrofit method declaration.

I use Retrofit 2.6.0.

[JakeWharton]

Not currently. I’m working on a parser for Kotlin metadata so we don’t have to depend on a gigantic jar to read one isNullable boolean.

On Thu, Apr 11, 2019, 8:27 PM Aidan Laing [e-mail] wrote:

Version: 2.6.0-SNAPSHOT Exception: KotlinNullPointerException Message: Response from {path to my suspend fun…} was null but response body type was declared as non-null

The current structure of my suspend fun in my service interface:

@POST(“api/…”) suspend fun request(@Body body: Body): Response?

I’m using Gson for serialization.

Is there a way to declare the response body type as nullable that I’m missing? I’ve tried adding null safety on my response object with ? and @Nullable with no success.

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/square/retrofit/issues/3075, or mute the thread https://github.com/notifications/unsubscribe-auth/AAEEEb6RFk0-5aDUMDF6fMlN9U2r9w7Hks5vf9MHgaJpZM4crGCw .