Status comming OK, but values aren't reaching to the server

[proyecto26]

Status comming OK, but values aren't reaching to the server

[itsharshdeep]

@jdnichollsc : I am really sorry for closing the issue bcz I know nothing about the help page you want me to add. I am only doing the front end part backend is doing some other freelancer.
So, its hard for me to say something like to him.

For now, I have used some other alternate plugin for the API functionality bcz that totally works fine.

But thanks once again for your contribution and making the plugin. :) 👍 💯

[jdnichollsc]

@itsharshdeep @davidorbelian after reviewing with NodeJS as the Backend, we can't send anonymous objects, a Serializable class is required. Example:

[Serializable]
public class ServerResponse {
  public string id;
  public DateTime date;
}
[Serializable]
public class User {
  public string firstName;
  public string lastName;
}
RestClient.Post<ServerResponse>("www.myapi.com/myendpoint", new User {
  firstName = "Juan David",
  lastName = "Nicholls Cardona"
}).Then(response => {
  EditorUtility.DisplayDialog("ID: ", response.id, "Ok");
  EditorUtility.DisplayDialog("Date: ", response.date.ToString(), "Ok");
});

Best regards, Nicholls

[jdnichollsc]

@itsharshdeep Can you install the nuget package Web Api Help Pages? I can't see any documentation of your service and I need to see how is your service getting the data of your request

[jdnichollsc]

Also the Content-Type application/json is added by default, so you don't need add that header again https://github.com/proyecto26/RestClient/blob/master/src/Proyecto26.RestClient/Utils/Extensions.cs#L25

[itsharshdeep]

Thanks a lot for quick response. But I didn't get "the nuget package Web Api Help Pages".
Can you please let me know in details. So that I can answer you well

[jdnichollsc]

@itsharshdeep from your web service https://www.nuget.org/packages/Microsoft.AspNet.WebApi.HelpPage/

[jdnichollsc]

?

[davidorbelian]

@itsharshdeep if your back end is made on ASP.NET, probably the issue is related with JsonUtility. I had the same issue and it was resolved when I replaced JsonUtility with Newtonsoft.Json one.