CODEWITHSUNDEEP
androidjsonretrofit
LEE
LEE

Reputation: 3605

Retrofit error expected BEGIN_OBJECT but was BEGIN_ARRAY

How can i parse this using retrofit? i'm getting the error BEGIN_OBJECT but was BEGIN_ARRAY

Right now, i'm parsing it this way..

Below is the adapter class

 public static RetroInterface getCommonPathInterface() {
        RestAdapter restAdapter = new RestAdapter.Builder()
                .setEndpoint("myurl")
                .build();
        records= restAdapter.create(RetroInterface.class);
        return records;
    }

Below is the interface, RetroInterface.class

 @GET("/mypath")
        void getValue(

                Callback<MyBean> callback    
        );

This is how i call it in the main activity

 getCommonPathInterface().getValue(new Callback<MyBean>() {
@Override
                    public void success(MyBean myBean, Response response) {
                       inti = 0;

                    }

                    @Override
                    public void failure(RetrofitError error) {
                        int i = 0;
                    }

                });

Below is the json response

 [
    {
    id: "111",
    name: "Val1"
    },
    {
    id: "222",
    name: "Val2"
    }
    ]

Upvotes: 0

Views: 3393

Answers (3)

LEE
LEE

Reputation: 3605

Yippi ! Got it working. Very simple solution. A small change in my callback method.

Instead of Callback<MyBean> callback used Callback<MyBean[]> callback. Problem solved ! :)

Upvotes: 2

Bhavdip Sagar
Bhavdip Sagar

Reputation: 1971

Hi Right now you are parsing the response as if it was formatted like this:

{
   "contacts":[
      {
         "id":"111",
         "name":"Val1"
      },
      {
         "id":"222",
         "name":"Val2"
      }
   ]
}

The exception tells you this in that you are expecting an object at the root but the real data is actually an array. This means you need to change the type to be an array to JSON object.

Thank you.

Upvotes: 1

Bruno Carrier
Bruno Carrier

Reputation: 532

I'm new to retrofit, but I was having this issue when I was dealing with a multi-class POJO and using code designed for a single-class POJO. Let me know if that's the case. Also, please paste a bit of code! :)

Upvotes: 0

Related Questions