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 Hosted app fails to run when Nuget Packages upgraded to 8.0.0-preview-4.23260.4 #86364

Closed
GraemeWellington opened this issue May 17, 2023 · 5 comments
Labels
arch-wasm WebAssembly architecture area-VM-meta-mono

Comments

@GraemeWellington
Copy link

GraemeWellington commented May 17, 2023

Description

Creating a new Blazor WASM Hosted app in version 8.0.0-preview-3.23177.8 works ok
Upgrading the Nuget Packages for Server/Client to version 8.0.0-preview-4.23260.4 fails to run

Console error: Reason: TypeError: r.withStartupOptions is not a function
at Wt (blazor.webassembly.js:1:54519)
(anonymous) @ blazor.webassembl

Reproduction Steps

Open Microsoft Visual Studio Community 2022 (64-bit) - Preview : Version 17.7.0 Preview 1.0
Create new project
Blazor WASM Hosted - this creates a project with .Net8 version: 8.0.0-preview-3.23177.8
Run the application - works ok
Upgrade Nuget Packages for Server / Client to 8.0.0-preview-4.23260.4
Run the application - fails to run {stops loading)

Console Error: Reason: TypeError: r.withStartupOptions is not a function
    at Wt (blazor.webassembly.js:1:54519)
(anonymous) @ blazor.webassembl

Expected behavior

Application should run as for previous version

Actual behavior

Application fails at loading state

Regression?

No response

Known Workarounds

No response

Configuration

No response

Other information

No response

@dotnet-issue-labeler dotnet-issue-labeler bot added the needs-area-label An area label is needed to ensure this gets routed to the appropriate area owners label May 17, 2023
@msftbot msftbot bot added the untriaged New issue has not been triaged by the area owner label May 17, 2023
@radical radical added arch-wasm WebAssembly architecture area-VM-meta-mono labels May 17, 2023
@msftbot
Copy link
Contributor

msftbot bot commented May 17, 2023

Tagging subscribers to 'arch-wasm': @lewing
See info in area-owners.md if you want to be subscribed.

Issue Details

Description

Creating a new Blazor WASM Hosted app in version 8.0.0-preview-3.23177.8 works ok
Upgrading the Nuget Packages for Server/Client to version 8.0.0-preview-4.23260.4 fails to run

Console error: Reason: TypeError: r.withStartupOptions is not a function
at Wt (blazor.webassembly.js:1:54519)
(anonymous) @ blazor.webassembl

Reproduction Steps

Open Microsoft Visual Studio Community 2022 (64-bit) - Preview : Version 17.7.0 Preview 1.0
Create new project
Blazor WASM Hosted - this creates a project with .Net8 version: 8.0.0-preview-3.23177.8
Run the application - works ok
Upgrade Nuget Packages for Server / Client to 8.0.0-preview-4.23260.4
Run the application - fails to run {stops loading)
Console Error: Reason: TypeError: r.withStartupOptions is not a function
at Wt (blazor.webassembly.js:1:54519)
(anonymous) @ blazor.webassembl

Expected behavior

Application should run as for previous version

Actual behavior

Application fails at loading state

Regression?

No response

Known Workarounds

No response

Configuration

No response

Other information

No response

Author: GraemeWellington
Assignees: -
Labels:

arch-wasm, untriaged, area-VM-meta-mono, needs-area-label

Milestone: -

@radical
Copy link
Member

radical commented May 17, 2023

cc @maraf @pavelsavara

@pavelsavara
Copy link
Member

Maybe clean and rebuild, clean browser cache ?

@lambdageek
Copy link
Member

@GraemeWellington Are you just upgrading the nuget references without installing the .NET 8 Preview 4 SDK?

@vcsjones vcsjones removed the needs-area-label An area label is needed to ensure this gets routed to the appropriate area owners label May 17, 2023
@GraemeWellington
Copy link
Author

GraemeWellington commented May 17, 2023 via email

@msftbot msftbot bot removed the untriaged New issue has not been triaged by the area owner label May 18, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
arch-wasm WebAssembly architecture area-VM-meta-mono
Projects
None yet
Development

No branches or pull requests

5 participants