Amal Francis

That would be a very nice idea as the mysql extension would be probably removed in near future....

for the time being is there any workaround for this?

I managed to find a workaround. ``` "start": "node_modules/@storybook/react/bin/index.js start-storybook -s ../web/public -p 9001 -c src", "start:mobile": "start-storybook -c src/mobile" ``` But it would be great if storybook by default...

It shows one story if I disable onDeviceUI. Though there is no way to navigate and the story is the top of device overlapping with battery indicator. At least it...

@dannyhw it's ``` AppRegistry.registerComponent(appName, () => StorybookApp); ``` this is inside react native index.js file. StorybookApp has config code that exports the view returned by getStorybookUI.

@dannyhw below is the code that I use. ``` configure(() => { loadStories(); }, module); addDecorator(addAppWrapper); // add some margin to prevent overlap with mobile header addDecorator(story => ( {story()}...

@dannyhw I use https://github.com/elderfo/react-native-storybook-loader and that function just imports the file generated by that package.

nope, it's still there. I use the version of storybook with the server. Don't use in-app anymore.

No, even if I import stories manually when in-app mode is used I get this error. Let me try with example app.

@chimmmpie Thanks for the suggestion. That would be a good feature to have. It needs to be checked whether all these registries are also expected to have same API endpoints...