All API calls failing due to JSON parse errors

[jkraemer]

As of today, all API calls using this gem started to fail due to JSON parse errors which were caused by the UTF8 BOM which you apparently have added to every response.

I worked around this by patching the gem / stripping the BOM out in case the initial parsing fails.
If this is an intended / permanent change to your API I could provide a proper fix / pull request.

Cheers,
Jens

[chrismaddocks]

We had JSON::Parser errors appear starting yesterday, too. They are no longer appearing, but we would be interested to know why the behaviour changed briefly yesterday, and if a more permanent gem fix is required.

[artempartos]

I had issue with parsing JSON, but the reason was that httpaty gem not decoding response when you set aceept-encoding header. It happens because since ruby 2 Net::Http encode/decode it by default, and you shouldn't add this header.
#55

[jrmhaig]

Is this the same as #58

[marcomarcianesi]

Is the problem back? I'm getting:

CreateSend::BadRequest: The CreateSend API responded with the following error - 400: Failed to deserialize your request

ruby 2.2.4

[marcomarcianesi]

I solved the issue above. The error was the shape of my payload, and the error message was totally misleading

[barrywoolgar]

@marcomarcianesi please could you explain what you mean by "shape of my payload"? I'm getting the same message even with very simple payloads. Many thanks

[seanmcoleman]

I'm also getting the same CreateSend::BadRequest: The CreateSend API responded with the following error - 400: Failed to deserialize your request error on very simple requests.

[rscherf]

For others experiencing this, I tried some of the ideas in this thread, however what worked for me was to just go back to v4.1.0, and everything worked. In my case I'm only updating subscribers, so I haven't tested how this change would affect other areas of the gem.

[tusharm]

@rscherf which version were you using earlier? Also, could you give details about the error you were getting?

[rscherf]

@tusharm we were using v5.1.0, doing a standard call to Subscriber#update. The API was the same:

The CreateSend API responded with the following error - 400: Failed to deserialize your request

[Xtinct]

Got the same error, the problem was in ConsentToTrack field value. I was passing true/false instead of Yes/No