POST using Retrofit is not returning to the Onresponse function

Question

My application is made with Kotlin Retrofit and Gson.

I have several gets to fetch information and work normally, manipulate the data returning in Onresponse and ok, works normally. But when I run as a POST this doesn’t happen, it never arrives in Onresponse. Json is sent correctly to the server, which returns 201 created status, but even then the Onresponse code is never executed, so I can’t control when the POST actually worked.

I wonder what’s wrong here?

Initializer:

private val retrofit = Retrofit.Builder()
        .baseUrl("http://myserverurl.com/api/")
        .addConverterFactory(GsonConverterFactory.create())
        .build()
fun orderService    ()  = retrofit.create(OrderService   ::class.java)

Orderservice.kt

interface OrderService {
    @POST("pedido")
    fun insert(@Body order: OrderEntity, @Header("mykey") myKey:String) : Call<OrderEntity>
}

Calling for:

val call = RetrofitInitializer().orderService().insert(order, mMyKey)
    call.enqueue(object : Callback<OrderEntity> {
        override fun onResponse(call: Call<OrderEntity>?,
                                response: Response<OrderEntity>?) {
            response?.body()?.let {
                Toast.makeText(mContext, "It works!", Toast.LENGTH_LONG).show()
            }
        }
        override fun onFailure(call: Call<OrderEntity>?, t: Throwable?) {
            Log.e("onFailure error", t?.message)
        }
    })

Remembering that the request works, only does not return pro onResponse.

Answer 1

I noticed something in its interface, in version 2 of the retrofit the data encoded by form are sent when @FormUrlEncoded. Each key value pair is annotated with @True of the name and the object providing the value. Make in the following pattern:

@FormUrlEncoded
@POST("Tokencelular")
Call<TokenModel> gravaToken(@Field("tokenDevice") String tokenDevice);

In your GET methods you don’t need.

To learn more, visit the documentation: https://square.github.io/retrofit/ and go to topic FORM ENCODED AND MULTIPART

Hugs!

Answer 2

I managed to solve it. Actually, the problem was quite another. Debugging better I realized that I was returning to Onresponse but with code 500, and then I discovered that one of the fields was giving a problem in the API that did not appear in my tests in Postman. The error was happening in the API’s Answer that was not converting a date value correctly, leading to 500 status even though it saved the record correctly.