-
Notifications
You must be signed in to change notification settings - Fork 248
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Failed to get message with JsonReaderException, when it is a forwarding appointment #2000
Comments
Thanks for raising this @bagdxk Any chance the result id different if you do not encode the message id?(as the SDK does handle encoding, double encoding may occur)
|
I tried to remove the UrlEncode and got same error.
|
Any chance you are able to share the contents of the response if you try this out to confirm if the response is indeed valid json? var requestInformation = graphClient.Me.Messages[msgId].ToGetRequestInformation();
var responseStream = await graphClient.RequestAdapter.SendPrimitiveAsync<Stream>(requestInformation);
using var streamReader = new StreamReader(responseStream);
var response = await streamReader.ReadToEndAsync();
Console.Write(response); |
Tested, the responsestream is null, in the code above. And try below code, the body is empty string. And confirmed the statuscode is 200.
|
Thanks for the getting back @bagdxk With the body is empty, any chance you can also confirm whether there is a value set for the content header? Ideally the serializer should be invoked if there is non-null content (which means there should also be no content type). response.Content.Headers.ContentType |
The contenttype is
|
Thanks @andrueastman the quick fix from client sdk side. |
Describe the bug
Calling below function, if the message is a forwarding appointment.
And get below error
To Reproduce
I am developing an outlook add-in, which call my web API to process mail messages.
Steps to reproduce the behavior:
Expected behavior
I expect the application can read the message, no exception.
Desktop (please complete the following information):
The text was updated successfully, but these errors were encountered: