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

After .NET 8 update appsettings.json.br not found after publishing to github pages #41

Closed
fingers10 opened this issue Nov 29, 2023 · 3 comments

Comments

@fingers10
Copy link
Contributor

fingers10 commented Nov 29, 2023

Hi @jsakamoto ,

I have updated my project to .NET 8 and published main branch of https://github.com/ILoveDotNet/ilovedotnet to github pages. I have noticed an runtime error which says appsettings.json.br is not found. The error is coming from brotliloader.min.js. This issue does not happen when publishing to IIS but happens when published to github pages.

Since the issue happened in production. I have reverted the .NET 8 upgrade. Howerver here is the .NET 8 commit link in main branch for your reference- ILoveDotNet/ilovedotnet@58b42ec

I remember we have already faced brotli issue in the past. Here is the previous issue reference - #22 (comment)

image

Please can you assist me on this? Feel free to let me know if any additional details are needed.

@fingers10 fingers10 changed the title appsettings.json.br not found after publishing to github pages After .NET 8 update appsettings.json.br not found after publishing to github pages Nov 29, 2023
@fingers10
Copy link
Contributor Author

Hi @jsakamoto any hints on this?

@jsakamoto
Copy link
Owner

Hi @fingers10,

I figured out that it is not a problem with the "BlazorWasmPreRendering.Build" package. It is a problem with the"PublishSPAforGitHubPages.Build" package. I fixed the problem that loading configurations fail on .NET 8 and published a new version of the "PublishSPAforGitHubPages.Build" package.

https://www.nuget.org/packages/PublishSPAforGitHubPages.Build/2.1.1#releasenotes-body-tab

I hope that the new package resolves the issue you reported here. Please try it out.

@fingers10
Copy link
Contributor Author

Many thanks @jsakamoto . That solved the issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants