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
Evidence that @storybook/react-native-server v 5.1.0-alpha.7 was working:
Usually when stories are "pending" (usually because the Simulator hasn't been opened yet - or it has been and storybook hasn't been refreshed since), then @storybook/react-native-server will simply show greyed-out divs as placeholder rows in the stories section, like so:
In the newest version, you can tell there's something different because now "pending" stories are simply non-existent:
Quick Fix
Reverting @storybook/react-native-server to 5.1.0-alpha.7
Since this quick fix exists, might be worth asking: why did I update the version in the first place? That was to address the issue created by the incorrect version recommendation in About Your Storybook as documented here: #6768
Describe the bug
@storybook/react-native-server
is broken in@storybook/[email protected]
. You can tell because none of the stories are displaying in the navbar.About Your Storybook
has a style issue@storybook/[email protected]
. Simulator screenshot:To Reproduce
Steps to reproduce the behavior:
@storybook/react-native-server
from version5.1.0-alpha.7
to5.1.0-beta.0
Expected behavior
@storybook/[email protected]
and@storybook/[email protected]
work togetherScreenshots
@storybook/react-native-server
v5.1.0-alpha.7
was working:@storybook/react-native-server
will simply show greyed-out divs as placeholder rows in the stories section, like so:Quick Fix
Reverting
@storybook/react-native-server
to5.1.0-alpha.7
Since this quick fix exists, might be worth asking: why did I update the version in the first place? That was to address the issue created by the incorrect version recommendation in
About Your Storybook
as documented here: #6768Ideal Fix
@storybook/[email protected]
and@storybook/[email protected]
work together.The text was updated successfully, but these errors were encountered: