Problem upgrading to Vaadin 25

I’ve just been trying to upgrade an app to Vaadin 25 and have struck a problem. The app compiles and starts, but after login nothing appears. Looking in the browser console log there is a request for a resource that gets a 404. This is a dynamic resource generated somewhere in the build.

GET http://127.0.0.1:9090/myApp/VAADIN/dynamic/resource/1/7bbbd548-233c-4be2-97f4-e772892c1a70/ 404 (Not Found)

How can I track down what is causing this or is this a Vaadin bug?

Using Windows 11/SpringBoot 4.0.1/Java 21

That URL belongs to a StreamResource or DownloadHandler in application code (or an add-on). While the 404 indicates some problem somewhere, it’s unlikely that this would cause the whole page to go blank. The 404 typically happens if the component owning the resource has disappeared, or if there’s some problems with cookies that causes the request to go to the wrong session.

A more likely cause after upgrading is incompatibility in some add-on or custom JavaScript in the application. Do you see any other errors in the browser’s JavaScript console, or errors from the JavaScript bundling process in the server-side log?