-
Notifications
You must be signed in to change notification settings - Fork 252
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
Graph SDK 5 HTTP request failed with System.IO.InvalidDataException "invalid data while decoding" #2205
Comments
Thanks for raising this @kyzhangZao Any chance you can provide some more information on the SDK version you are using and the sample code of the request you are making as well as how you are initializing the client? |
Hi @andrueastman , I'm using graph sdk Version="5.32.0" A sample request of fetching group is like And for graph client initialization We're a 1p App, so the flow should be within each graph call, we'll include the bearer token issued by msGraph with the preauth permission we've requested. |
@kyzhangZao |
Hi @andrueastman , No we have no customization of compression handling.
These are the only modification we had on the handler. |
The compression handler seems to be introduced in the sdk itself from its dependency Kiota. I just tried, directly remove the compression handler within our service setup actually fixed this issue. But would like to check if this is something we should do/would there be any consequences if we remove this handler? |
Hey @kyzhangZao, Any chance you can confirm(or share a reference) if the
Removing the |
This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for 4 days. It will be closed if no further activity occurs within 3 days of this comment. |
To test the graph sdk upgrade change in our testing environment, all the graph calls failed with System.IO.InvalidDataException "invalid data while decoding"
One sample full traces on our end looks like:
This error message is not super helpful, and we're not able to understand what's the exactly issue here. But it seems related with the Kiota HTTP dependency being introduced in the upgrade.
As making http request being mentioned https://github.com/microsoftgraph/msgraph-sdk-dotnet/blob/feature/5.0/docs/upgrade-to-v5.md#removal-of-request-from-the-fluent-api, I'm following this guidance. Hence need some hints of how to fix this issue.
The text was updated successfully, but these errors were encountered: