Blazor WASM InteractiveRequestOptions is ignored when deployed to Azure #45289
Labels
area-blazor
Includes: Blazor, Razor Components
feature-blazor-wasm
This issue is related to and / or impacts Blazor WebAssembly
feature-blazor-wasm-auth
✔️ Resolution: Duplicate
Resolved as a duplicate of another issue
Status: Resolved
Comments
javiercn
added
area-blazor
|
@darena-pjindal thanks for contacting us. This is a known issue with regards to trimming in .NET 7.0. We have addressed the issue in 7.0.1 which will be available in a few weeks. In the mean time, you can disable trimming for the assembly. See #44973 (comment) for details. Dupe of #44973 |
javiercn
added
the
✔️ Resolution: Duplicate
ghost
locked as resolved and limited conversation to collaborators
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Is there an existing issue for this?
Describe the bug
I have created a default blazor wasm project in .net7 with authentication. I added the InteractiveRequestOptions with a returnURL to counter page. This works with no issues locally. However, if I deploy this to Azure web app (hosted or not hosted), the interactiverequestoptions are being completely ignored. It just redirects it to the home page. Is there some additional configuration required to maintain the HistoryEntryState once deployed to Azure
Expected Behavior
No response
Steps To Reproduce
No response
Exceptions (if any)
No response
.NET Version
7
Anything else?
No response
The text was updated successfully, but these errors were encountered: