Upgrading to 19.1.25.521 Breaks Project Due to Licensing Issues
Environment
| Product | Progress® Telerik® Reporting |
| Version | 19.1.25.521 |
Description
After upgrading to Telerik Reporting version 19.1.25.521, the project fails due to licensing issues. The problem is specific to the Edge browser and is resolved in incognito mode. Hard-refreshing the browser resolves the issue, but concerns arise about users encountering caching problems after deployment. You want to ensure that the browser loads the latest JavaScript files without caching old resources.
Solution
To resolve the issue, follow these steps:
- Perform a hard refresh by pressing
CTRL+F5in the Edge browser. - If the hard refresh doesn’t work:
- Open the browser's DevTools (
F12or right-click and select "Inspect"). - Navigate to the "Network" tab.
- Check the "Disable cache" checkbox.
- Restart the browser and perform another hard refresh (
CTRL+F5).
- Open the browser's DevTools (
- Verify that all JavaScript resources are returned with a status code 200, indicating no cache usage.
To avoid similar problems for end-users after deployment, use a cache-busting technique by appending a query string (e.g., version or timestamp) to the script URLs. For example:
<script src="_content/Telerik.UI.for.Blazor/js/telerik-blazor.js?v=1.1"></script>
<script src="_content/Telerik.ReportViewer.BlazorNative/js/reporting-blazor-viewer.js?v=1.1"></script>
This forces browsers to reload the updated files.