-
Notifications
You must be signed in to change notification settings - Fork 491
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
NullReferenceException on Gateway mode on WebAssembly #1873
Comments
Apparently HttpClient in WASM does not set the HttpResponseMessage.RequestMessage property when
After this call, One potential quick fix would be to add this on
@j82w What do you think? I'm trying to create a small repro for the NET team and will file it in their repo. |
Filing in their repo is fine - but this would take forever to get rolled out. So making the change proposed to safe-guard in our code is definitely a good choice. |
I agree that we should file it on their repo, but also do the fix the SDK to unblock users. |
Related: dotnet/runtime#42691 |
Closing due to in-activity, pease feel free to re-open. |
When doing a point operation over a non- existent container generates a NullReferenceException.
Steps to reproduce
Yields this stack trace:
SDK 3.13.0 running on Blazor Web Assembly
Can't repro on a normal NET Core application, but it seems the NRE comes from this line:
string resourceLink = responseMessage.RequestMessage.RequestUri.LocalPath;
, responseMessage.RequestMessage seems to be null.The text was updated successfully, but these errors were encountered: