using `configure` leads to CSF story not showing in the stories list until hot reload is triggered about react-native HOT 4 CLOSED

Great, thanks for the insights! This was a bit of a pickle and I'm glad I'm now past this issue. I wonder if it would make sense to emit a warning when configure is called more than once (as it was in my case), which could help future devs who are upgrading older projects.
Will close this issue for now.

from react-native.

@flochtililoch the configure function gets called in the generated code inside storybook.requires.js and shouldn't be directly called in your code.

from react-native.

@dannyhw Interesting, I've had this code configured this way since our first install of storybook 6 years ago, I must have missed this during my latest migration, though I don't remember this being called out on the migration steps.
Is the intention for configure to be called only once and by storybook.requires only?

from react-native.

@flochtililoch yes it's intended because now we generate your imports and configure should never be called twice otherwise it would cause those weird behaviours. This will enable some cool changes in v7 too.

In the official blog for the release the first step does briefly mention removing the configure call but perhaps its not super clear https://storybook.js.org/blog/storybook-for-react-native-6-5/

from react-native.