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 deployment to AWS S3 was working now failing with "Failed to find a valid digest in the 'integrity' attribute for resource" #52942

Closed
1 task done
baynezy opened this issue Dec 21, 2023 · 2 comments
Labels
area-blazor Includes: Blazor, Razor Components

Comments

@baynezy
Copy link

baynezy commented Dec 21, 2023

Is there an existing issue for this?

  • I have searched the existing issues

Describe the bug

A new deployment of Blazor WASM to AWS S3 is now failing with "Failed to find a valid digest in the 'integrity' attribute for resource"

Expected Behavior

The application should be updated and working correctly.

Steps To Reproduce

  • Deploy WASM application in AWS S3 with CloudFront. This works.
  • Publish a new version with changes
  • Overwrite the existing files in S3 aws s3 sync ./web-publish/wwwroot s3://bucket-name --delete

Exceptions (if any)

All the .wasm files are reporting that Failed to find a valid digest in the 'integrity' attribute for resource

.NET Version

8.0.100

Anything else?

The application works fine for local development.

@dotnet-issue-labeler dotnet-issue-labeler bot added the area-blazor Includes: Blazor, Razor Components label Dec 21, 2023
@javiercn
Copy link
Member

@baynezy thanks for contacting us.

Check that the files are being downloaded correctly in the network tab (you are not getting 404) and check that you have correctly configured your caching directives.

@baynezy
Copy link
Author

baynezy commented Dec 21, 2023

@javiercn thanks for your input. They were all returning 200 properly it just was failing with the aforementioned error.

Without making any changes it's resolved itself. So I'm pretty sure it's due to CloudFront caching. So I'll close this issue. Sorry to bother you, and thanks again.

@baynezy baynezy closed this as completed Dec 21, 2023
@ghost ghost locked as resolved and limited conversation to collaborators Feb 6, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
area-blazor Includes: Blazor, Razor Components
Projects
None yet
Development

No branches or pull requests

2 participants