Ofc, the issue can easily be solved by installing System.Text.Encodings.Web in version 8.0.0 manually, but I guess it would be better to have the package working by default, right?
Could that dependency be upgraded in the SDK directly to avoid this?
We are going to take a look at it - similar to this post last week.
It won't be done immediately (I mean not a matter of days). There are other dependencies that may cause the same issue with this circular dependency when we update (from RestSharp or from System.Runtime.CompilerServices.Unsafe). But we have this on the radar now (an internal ticket has been created).
If you don't mind using your workaround approach until we try to do this in a clean way, it'd be great.
I'll update this post when I have some news/updates.
No worries. This was not to tell you you had done something wrong
But that we had heard of this circular dependency issue.
We would like to see if we can keep some of the dependencies in 8.x.
A new version of the SDK (228) has been released today, with an update of the dependencies. Let me know if that solves your issue (or if I have introduced another one ).
