Skip to content

.NET Core 3.0 Preview 7 - Blazor App - GET /_framework/blazor.boot.json (similar to #1469) #12637

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

Closed
bartczernicki opened this issue Jul 26, 2019 · 2 comments
Assignees
Labels
area-blazor Includes: Blazor, Razor Components ✔️ Resolution: Duplicate Resolved as a duplicate of another issue investigate

Comments

@bartczernicki
Copy link

#11897 Describe the bug
404 Error - GET /_framework/blazor.boot.json (Similar to #1469)

To Reproduce

Steps to reproduce the behavior:

  1. Using this version of ASP.NET Core '.Net Core 3.0 Preview 7 with new SignalR NuGet'

  2. Run this code:
    https://github.com/bartczernicki/MachineLearning-BaseballPrediction-BlazorApp
    Deployed here (App Service with SignalR)
    https://baseballpredictionblazor.azurewebsites.net/baseballprediction

  3. With these arguments: Select the fake player or move slider. Sometimes on first load in 'preview 7' it just hangs and requires a Ctrl+F5 reload

  4. See error

Expected behavior

No hanging app on first load

Additional context

Don't remember this happening in preview 6 or earlier. But then again App Insights with Blazor had issues (it would just stop working). Preview 7 .net core 3.0 it works fine.

I work at Microsoft, so can debug internally as well.

@bartczernicki bartczernicki changed the title GET /_framework/blazor.boot.json (similar to #1469) .NET Core 3.0 Preview 7 - Blazor App - GET /_framework/blazor.boot.json (similar to #1469) Jul 26, 2019
@mkArtakMSFT mkArtakMSFT added area-blazor Includes: Blazor, Razor Components investigate labels Jul 29, 2019
@mkArtakMSFT mkArtakMSFT modified the milestones: 3.0.0-rc1, 3.1.0 Jul 29, 2019
@mkArtakMSFT
Copy link
Member

Thanks for contacting us, @bartczernicki.
We're heads down finalizing the upcoming 3.0 release and we'll be able to look into this post 3.0.

@pranavkm
Copy link
Contributor

@bartczernicki it's fairly likely you were running in to #11560. I tried playing around with your deployed application now and could not reproduce the error.

@pranavkm pranavkm removed this from the 5.0.0-preview1 milestone Aug 26, 2019
@pranavkm pranavkm added the ✔️ Resolution: Duplicate Resolved as a duplicate of another issue label Aug 26, 2019
@ghost ghost locked as resolved and limited conversation to collaborators Dec 2, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
area-blazor Includes: Blazor, Razor Components ✔️ Resolution: Duplicate Resolved as a duplicate of another issue investigate
Projects
None yet
Development

No branches or pull requests

3 participants