WARNING: Processing source-maps of Telerik.ReportViewer.BlazorNative/js/reporting-blazor-viewer.js took longer than 11000 ms

Progress® Telerik® Reporting Feedback Portal

Create an account Log In

Back to Feed

Request a Feature Report a Bug

Unplanned

Last Updated: 31 Aug 2023 15:15 by Marc

Marc

Created on: 31 Aug 2023 12:42

Type: Bug Report

WARNING: Processing source-maps of Telerik.ReportViewer.BlazorNative/js/reporting-blazor-viewer.js took longer than 11000 ms

The following warning is shown in the browser console when starting my Blazor application when I use the native Blazor Report Viewer:

WARNING: Processing source-maps of https://localhost:7025/_content/Telerik.ReportViewer.BlazorNative/js/reporting-blazor-viewer.js took longer than 11000 ms so we continued execution without waiting for all the breakpoints for the script to be set.Could not read source map for https://localhost:7025/_content/Telerik.ReportViewer.BlazorNative/js/reporting-blazor-viewer.js: Unexpected 404 response from https://localhost:7025/_content/Telerik.ReportViewer.BlazorNative/js/reporting-blazor-viewer.js.map:

1 comment

Marc

Posted on: 31 Aug 2023 15:15

Modify the JavaScript File

Open reporting-blazor-viewer.js and look for a comment line at the end that specifies the .map file. It should look something like this:

//# sourceMappingURL=reporting-blazor-viewer.js.map

Delete that line and save the file. This tells the debugger that no .map file is associated with the .js file.

For the time being, do this or add an empty .map file:

Generate an Empty .mapFile

You can try creating an empty .map file and placing it in the same directory where reporting-blazor-viewer.js resides. Make sure to name the .map file exactly as the system expects it: reporting-blazor-viewer.js.map. This should trick the system into thinking it has found the .map file it's looking for, potentially eliminating the 404 error.