You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Sometimes when running Storybook for the first time of the day, it opens the browser with a "No Preview" error (404 for story url).
Then you need to switch between stories a couple of times till they are actually rendered.
I believe you can just use sb repro and select any framework, then run it for the first time. That should get you to the error. Another way that I found to reproduce a similar behavior is to:
1 - Open a storybook normally (you can use this deployed one for experimentation)
2 - Change url to wrong story name
3 - Get the 404 "No preview" screen
4 - When switching stories one time, you see that it won't render correctly (it does load the args though).
My assumption is that sometimes when initialising Storybook, the initial story is not loaded correctly, giving the 404 screen, and then you have this situation where you need to select another story, and still you have the 404 page, until you select a second story, then it works.
404-error.mp4
The text was updated successfully, but these errors were encountered:
I think the first 404 might be caused by running Storybook on a port you've already run it on in the past, and some kind of caching there. We see it from time to time because we run a lot of different Storybooks on typical ports (e.g. 6006) but I don't think most users experience that.
The second click concerns me more because it's clearly loading the story at some level but not displaying it properly.
Describe the bug
Sometimes when running Storybook for the first time of the day, it opens the browser with a "No Preview" error (404 for story url).
Then you need to switch between stories a couple of times till they are actually rendered.
This was once reported in #14376
To Reproduce
I believe you can just use
sb repro
and select any framework, then run it for the first time. That should get you to the error. Another way that I found to reproduce a similar behavior is to:1 - Open a storybook normally (you can use this deployed one for experimentation)
2 - Change url to wrong story name
3 - Get the 404 "No preview" screen
4 - When switching stories one time, you see that it won't render correctly (it does load the args though).
My assumption is that sometimes when initialising Storybook, the initial story is not loaded correctly, giving the 404 screen, and then you have this situation where you need to select another story, and still you have the 404 page, until you select a second story, then it works.
404-error.mp4
The text was updated successfully, but these errors were encountered: