You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We just started receiving the following exception in production:
"Type": "SerializationException",
"Message": "Invalid JSON string",
"Source": "Facebook",
"StackTrace": " at Facebook.SimpleJson.DeserializeObject(String json)\r\n at Facebook.SimpleJson.DeserializeObject(String json, Type type, IJsonSerializerStrategy jsonSerializerStrategy)\r\n at Facebook.SimpleJson.DeserializeObject(String json, Type type)\r\n at Facebook.FacebookClient.ProcessResponse(HttpHelper httpHelper, String responseString, Type resultType, Boolean containsEtag, IList`1 batchEtags)\r\n at Facebook.FacebookClient.Api(HttpMethod httpMethod, String path, Object parameters, Type resultType)\r\n at Facebook.FacebookClient.Post(String path, Object parameters)\r\n at ... ",
This occurs during the following call:
var result = fbClient.Post(path, post);
The problem seems to occur with the result coming back from Facebook, after a successful post. Did Facebook change their API response? Looking for an updated version that can handle the response correctly.
The text was updated successfully, but these errors were encountered:
Seems to be a bug from Facebook - returning a null value back instead of the id. The cause seems to be an 'Expect 100-continue' header. Does the client send this header?
----- full source-----
var path = string.Format("{0}/feed", fbAccount.Id);
var resultId = string.Empty;
dynamic post = new ExpandoObject();
post.message = content.Message;
var result = fbClient.Post(path, post);
resultId = result.id;
It is happening with every post (it seems). I could reproduce it with a super simple example.
We just started receiving the following exception in production:
The problem seems to occur with the result coming back from Facebook, after a successful post. Did Facebook change their API response? Looking for an updated version that can handle the response correctly.
The text was updated successfully, but these errors were encountered: