Skip to content
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

Blazor wasm local storage not working when started from VS IDE 16.6.0 Preview 5&6 #75

Closed
intech-paul opened this issue May 9, 2020 · 3 comments
Labels
Bug Something isn't working Resolved: Won't Fix The reported behaviour will not be changed.

Comments

@intech-paul
Copy link

Breaking change on 16.6.0 preview 5&6

When you start a blazor wasm app from the vs ide, it can't see any local storage values. It can save and then see its own storage values. Then if you close the app & start it again from the ide, the storage data is not there.

If the app is started directly from chrome using localhost address, the local storage works properly.

An issue has been created with the VS team:
dotnet/aspnetcore#21642

@intech-paul intech-paul added Bug Something isn't working Triage Issue needs to be triaged labels May 9, 2020
@chrissainty
Copy link
Member

Thanks for the heads up on this @intech-paul. It seems it’s more a potential bug with VS than us, is that correct?

@chrissainty
Copy link
Member

As I've not heard back I'm going to close this issue as there doesn't appear to be anything for us to do.

@chrissainty chrissainty added Resolved: Won't Fix The reported behaviour will not be changed. and removed Triage Issue needs to be triaged labels May 14, 2020
@intech-paul
Copy link
Author

This issue has been corrected in the latest update of Visual Studio:
Version 16.7.0 Preview 1.0

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug Something isn't working Resolved: Won't Fix The reported behaviour will not be changed.
Projects
None yet
Development

No branches or pull requests

2 participants