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 project started from visual studio run clears browser local storage #21642

Closed
vsfeedback opened this issue May 8, 2020 · 1 comment
Labels
area-blazor Includes: Blazor, Razor Components Author: Migration Bot 🤖 The issue was created by a issue mover bot. The author may not be the actual author. feature-blazor-wasm This issue is related to and / or impacts Blazor WebAssembly

Comments

@vsfeedback
Copy link

This issue has been moved from a ticket on Developer Community.


[regression] [worked-in:16.6.5]
When an app is started by running it from visual studio, the local storage values are cleared (test default new blazor project that does not access local storage in any way) - just as a test as I noticed my main program started to drop the local storage settings.

**If the blazor app is run directly from a google chrome browser, the local storage values are there.

If I then start app from IDE, no settings, and then start again from browser the settings are still there.


Original Comments

paul on 5/3/2020, 03:47 PM:

Any update on this ?

The local storage can be written to /read while the blazor wasm app is running. But if it is closed and started again from withing the vs ide, the local storage is all blank. All normal when the app is started with a chrome browser shortcut on the desktop. (i.e https://localhost:44370/)

Using chrome browser, vs updated to latest version/ all blazor packages to latest version.

Visual Studio Feedback System on 5/4/2020, 00:35 AM:

We have directed your feedback to the appropriate engineering team for further evaluation. The team will review the feedback and notify you about the next steps.


Original Solutions

(no solutions)

@ghost ghost added the Author: Migration Bot 🤖 The issue was created by a issue mover bot. The author may not be the actual author. label May 8, 2020
@mkArtakMSFT mkArtakMSFT added area-blazor Includes: Blazor, Razor Components feature-blazor-wasm This issue is related to and / or impacts Blazor WebAssembly labels May 8, 2020
@mkArtakMSFT
Copy link
Member

Thanks for contacting us. This is going to be fixed in the VS 16.6 release. Closing this, as the issue has been fixed on the VS side.

@ghost ghost locked as resolved and limited conversation to collaborators Jun 10, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
area-blazor Includes: Blazor, Razor Components Author: Migration Bot 🤖 The issue was created by a issue mover bot. The author may not be the actual author. feature-blazor-wasm This issue is related to and / or impacts Blazor WebAssembly
Projects
None yet
Development

No branches or pull requests

2 participants