Description:
I am experiencing a bug in Google Stitch where new screens fail to appear on the canvas, or become permanently stuck in a “generating” state. The generation logs indicate that the screen creation was successful, but the frontend fails to render it.
Upon inspecting the browser console, I found that the frontend is crashing during the layout rendering phase because it fails to load a generated image asset.
Error Log Details:
The console throws the following error, stopping the screen injection completely: Error in updateScreensWithSessions: Error: Failed to load image from data URI (...) File: util-WAbyGcxJ.js Function: updateScreensWithSessionsInternal → layoutsSession
(See below image for the full trace).
Steps to Reproduce:
-
Submit a prompt to generate a new screen.
-
Wait for generation logs to report success.
-
Observe the canvas UI either remains stuck in the generating animation or fails to display the new screen entirely, accompanied by the console error mentioned above.
System Info:
- ASUS ROG Strix G16 (Intel Core i7 14th Gen, RTX 5050)
Workarounds I Tried:
Refreshing the page or clearing the cache does not resolve the broken screen. Selecting the stuck screen and clicking “Regenerate” also does not bypass the corrupted image generation, because most of the time, the generated screens do not even appear on the canvas. Duplicating the project seems to be the only workaround that unfreezes the canvas, though even that fails occasionally.
Any help looking into the updateScreensWithSessions image parsing would be greatly appreciated!