Skip to content

Commit

Permalink
docs(common)troubleshooting - add Failed to find error (#2053)
Browse files Browse the repository at this point in the history
* docs(common)troubleshooting - add Failed to find error

* Update knowledge-base/common-failed-to-find.md

Co-authored-by: Yordan <60105689+yordan-mitev@users.noreply.github.com>

* Update knowledge-base/common-failed-to-find.md

Co-authored-by: Yordan <60105689+yordan-mitev@users.noreply.github.com>

* Update knowledge-base/common-failed-to-find.md

Co-authored-by: Yordan <60105689+yordan-mitev@users.noreply.github.com>

* update after review

* Update knowledge-base/common-failed-to-find.md

Co-authored-by: Dimo Dimov <961014+dimodi@users.noreply.github.com>

* Update knowledge-base/common-failed-to-find.md

Co-authored-by: Dimo Dimov <961014+dimodi@users.noreply.github.com>

* Update knowledge-base/common-failed-to-find.md

Co-authored-by: Dimo Dimov <961014+dimodi@users.noreply.github.com>

* update after review

* fix wrong slug and list resources

* Update knowledge-base/common-failed-to-find.md

Co-authored-by: Dimo Dimov <961014+dimodi@users.noreply.github.com>

* Update troubleshooting/general-issues.md

Co-authored-by: Dimo Dimov <961014+dimodi@users.noreply.github.com>

* reword the link text

* reword the link text and add key words

---------

Co-authored-by: Yordan <60105689+yordan-mitev@users.noreply.github.com>
Co-authored-by: Dimo Dimov <961014+dimodi@users.noreply.github.com>
  • Loading branch information
3 people committed Apr 30, 2024
1 parent 4031961 commit bfd3c4d
Show file tree
Hide file tree
Showing 2 changed files with 61 additions and 0 deletions.
56 changes: 56 additions & 0 deletions knowledge-base/common-failed-to-find.md
@@ -0,0 +1,56 @@
---
title: Failed To Find a Valid Digest in the 'Integrity' Attribute
description: Learn what causes the Failed to find a valid digest in the 'integrity' attribute for resource ... with computed SHA-256 integrity ... error and how to fix it.
type: troubleshooting
page_title: Failed To Find a Valid Digest in the 'Integrity' Attribute
slug: common-kb-failed-to-find
tags: telerik, blazor, troubleshooting, webassembly
ticketid: 1645828, 1495720, 1540839, 1557096, 1557819, 1587286, 1615743, 1617356, 1636012
res_type: kb
---

## Environment

<table>
<tbody>
<tr>
<td>Product</td>
<td>UI for Blazor</td>
</tr>
</tbody>
</table>

## Description

I get a `Failed to find a valid digest in the 'integrity' attribute for resource ... with computed SHA-256 integrity ...` error after upgrading the `Telerik.UI.for.Blazor` NuGet package and publishing my Blazor WebAssembly app.

## Error Message

>warning Failed to find a valid digest in the 'integrity' attribute for resource 'https://.../_framework/Telerik.Recurrence.dll' with computed SHA-256 integrity ... The resource has been blocked.
>
> Unknown error occured while trying to verify integrity.
>
>Error: Failed to start platform. Reason: TypeError: Failed to fetch
Other possible resources that may be referred to in the error:
* Telerik.Documents.SpreadsheetStreaming.dll
* Telerik.DataSource.dll
* Telerik.Zip.dll
* Telerik.Blazor.dll
* Telerik.FontIcons.dll
* Telerik.SvgIcons.dll


## Cause

The exception is a general Blazor WebAssembly issue, which can result from the build process, publishing process, or browser cache. The Telerik UI for Blazor components are not related to the problem.

## Solution

The fix for the exception can vary, depending on the cause. Here are some online documentation and discussions on the matter, which suggest possible solutions:

* https://learn.microsoft.com/en-us/aspnet/core/blazor/host-and-deploy/webassembly?view=aspnetcore-5.0#resolve-integrity-check-failures
* https://stackoverflow.com/questions/69926878/failed-to-find-a-valid-digest-in-the-integrity-attribute-for-resource-in-blazo
* https://stackoverflow.com/questions/62063983/cant-run-published-blazor-webassembly-app
* https://stackoverflow.com/questions/61562422/wasm-dotnet-integrity-attribute-invalid-for-my-blazor-app-on-github-pages
* https://stackoverflow.com/questions/66063159/random-blazor-failed-to-find-a-valid-digest-in-the-integrity-attribute-for-re
5 changes: 5 additions & 0 deletions troubleshooting/general-issues.md
Expand Up @@ -18,6 +18,7 @@ This page provides solutions for common issues you may encounter while working w
* [Unable to find package Telerik.Documents.SpreadsheetStreaming](#unable-to-find-package-telerikdocumentsspreadsheetstreaming)
* [Cannot provide a value for property 'Localizer'](#cannot-provide-a-value-for-property-localizer)
* [Slow Performance](#slow-performance)
* [Failed to find a valid digest in the 'integrity' attribute for resource ... with computed SHA-256 integrity ...](#failed-to-find-a-valid-digest-in-the-integrity-attribute-for-resource--with-computed-sha-256-integrity)
* [JavaScript errors]({%slug troubleshooting-js-errors%})
* [Issues after deployment]({%slug deployment-troubleshooting%})
* [Content Security Policy]({%slug troubleshooting-csp%})
Expand Down Expand Up @@ -128,6 +129,10 @@ There are also certain measures a web app should take to improve its performance

* If you need to generate documents or prepare some data, try to offload this task to the server. You can create an HTTP request and gather the processed information. With this approach, you will gain from the better server-side performance and won't download all the data on the client-side. You can find an example of the approach in the <a href="https://github.com/telerik/blazor-ui/tree/master/grid/pdf-export-server" target="_blank">Export Grid to PDF on the Server</a> sample project.

## Failed to find a valid digest in the 'integrity' attribute for resource ... with computed SHA-256 integrity ...

The error is a general Blazor WebAssembly issue, which can result from the build process, publishing process, or browser cache. Our [knowledge base article about the `Failed to find a valid digest in the 'integrity' attribute` exception]({%slug common-kb-failed-to-find%}) contains discussions and documentation with possible solutions.


## See Also

Expand Down

0 comments on commit bfd3c4d

Please sign in to comment.