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 are experiencing a similar issue, while building a request. It does work on some machines but not on the others. Presumably the issue is on Windows10, Windows 11 works ok.
System.MissingMethodException: Attempted to access a missing method.
at Refit.SystemTextJsonContentSerializer.ToHttpContent[T](T item)
at Refit.RequestBuilderImplementation.AddBodyToRequest(RestMethodInfoInternal restMethod, Object param, HttpRequestMessage ret) in c:\temp\releaser\refit\Refit\RequestBuilderImplementation.cs:line 888
at Refit.RequestBuilderImplementation.<>c__DisplayClass19_0.<BuildRequestFactoryForMethod>b__0(Object[] paramList) in c:\temp\releaser\refit\Refit\RequestBuilderImplementation.cs:line 683
at Refit.RequestBuilderImplementation.<>c__DisplayClass15_0`2.<<BuildCancellableTaskFuncForMethod>b__0>d.MoveNext() in c:\temp\releaser\refit\Refit\RequestBuilderImplementation.cs:line 320
--- End of stack trace from previous location ---
Describe the bug 🐞
Getting this error on a .NET 8 Blazor Web App, when render mode gets to WASM.
crit: Microsoft.AspNetCore.Components.WebAssembly.Rendering.WebAssemblyRenderer[100]
Unhandled exception rendering component: Method not found: System.Threading.Tasks.Task
1<Refit.ApiResponse
1<!0>> Refit.ApiResponse1.EnsureSuccessfulAsync() System.MissingMethodException: Method not found: System.Threading.Tasks.Task
1<Refit.ApiResponse1<!0>> Refit.ApiResponse
1.EnsureSuccessfulAsync()at System.Runtime.CompilerServices.AsyncMethodBuilderCore.Start[d__14](d__14& stateMachine)
Step to reproduce
Reproduction repository
https://github.com/reactiveui/refit
Expected behavior
Method should be present and request being verified
Screenshots 🖼️
No response
IDE
No response
Operating system
No response
Version
No response
Device
No response
Refit Version
No response
Additional information ℹ️
No response
The text was updated successfully, but these errors were encountered: