[TypeError] Object is not a constructor

[saulojoab]

What version of React, ReactDOM/React Native, Redux, and React Redux are you using?

• React: 18.0.0
• ReactDOM/React Native: ^0.70.1
• Redux-Toolkit: ^1.9.1
• React Redux: ^8.0.5

What is the current behavior?

Whenever I create my store on the App entry point, I get this error:

Error loading story index:
[TypeError] Object is not a constructor

This error does not spawn a Logbox with errors, but it breaks some of my app's libraries. As an example, Apollo requests always return undefined, and react-native-image-crop-picker does not work correctly.

This is my entry point stack:

I think its probably something to do with a library conflict or something, but it's making my head burn trying to solve it. I've tried everything: moving the provider location, adding it onto the index.js file, with no success.

This is my store configuration:

This is one of my reducers:

What is the expected behavior?

Everything should work without breaking the app.

Which browser and OS are affected by this issue?

Android - API Level 33

Did this work in previous versions of React Redux?

• Yes

[phryneas]

Maybe wrap a

try {
  //...
} catch (e) {
  console.log(e.toString(), e.stack.toString());
  throw e;
}

around it. With the given information it's pretty impossible to say anything.

[saulojoab]

@phryneas where should I put the try-catch?

That's what confused me the most, since the error doesn't show where the root cause is, not on the Logbox, RN dev tools and Flipper.

[phryneas]

Around the place that you assume causes the error. If you say it happens when creating the store, wrap it around configureStore.

[saulojoab]

@phryneas I did this, and it didn't throw any errors:

It's very hard to find the cause since the error does not specify where it comes from. Maybe it is something with redux-toolkit?

[timdorr]

This doesn't appear to be a bug with Redux or RTK.

Like Lenz said, you can do that wrapping to track down the source of the error. The storybook one is probably a good place to start. Go into your node_modules folder and find this code (after transpilation) to add the more descriptive error handling there (particularly e.stack).

[saulojoab]

just in case anyone stumbles upon this: it was Storybook.

I don't know why it breaks, but removing the Storybook imports solved the problem. Really weird.