Replies: 1 comment
-
This was an issue with CSLA and the enhanced state management subsystem for Blazor. To my knowledge it is resolved in the current version of CSLA. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
This issue should have nothing to do with csla , Read an article on the Rockford blog "Accessing User Identity on a Blazor Wasm Client",I tried to add this functionality to my own blazor server application by following the steps in the article and adding the appropriate code and pages ,I'm just trying to simulate the user's Login, but when I use SignInAsync,


I get an error "Headers are read-only, response has already started." My login page is rendered in default mode. Does anyone know about this?
Beta Was this translation helpful? Give feedback.
All reactions