redux-thunk | Thunk middleware for Redux | State Container library

We have fixed the issue by replacing

You can simply call store.getState() method to get the current state tree of your application. It is equal to the last value returned by the store's reducer.

Had this same error. Couldn't figure it out the cause, but downgrading to redux-thunk@2.3.0 solved it for me.

I'd recommend giving the official Redux Style Guide a read.

Generally: at this moment, there are 14818 redux-themed packages available on npm. It's pretty impossible to name them all ;)

But also, there are clear recommendations by the Redux team:

• use Redux Toolkit
• if you only need api data without further manual logic, use createApi form RTK-Query
• if you need manual logic attached to that, use createAsyncThunk or just thunks. Only if those are not enough, turn to other middlewares like saga
• sagas are very overused, most of the time not needed and add unneccesary complexity. We are currently building an action-listener-middleware that covers about 75% of the saga functionality with a simpler api (those 25% functionality left after that are the real saga use case, but probably only 2-5% of users ever need those).
  That said, most people would not even need that and could probably do everything they are using sagas for with thunks instead, which are much more simple.

There are also other libraries like redux-observable etc. Those have a non-deniable market share in the single-digit percentages, but if you are just getting started, go by the official recommendations.

Best get started by reading the official Redux Tutorial. It should cover 90% of all the Redux knowledge you'll ever need.

PRODUCT_LIST_REQUEST appears to be a string. You cannot dispatch a string by itself - only action objects. Actions are always objects that have a type field inside, like {type: 'counter/incremented'}.

That said, you should be using our official Redux Toolkit package to write your Redux code. Redux Toolkit will simplify all of the Redux store setup and reducer logic you've shown.

Those are peer dependencies, not actual dependencies. Here is a good article explaining the difference. Peer dependencies are just to let users know what versions of various packages your installed package is compatible with. You don't need to fix these issues, as they are just letting you know which versions of various packages are compatible IF you want to use those packages sometime in the future.

In short, you can just start you project as-is, there is nothing that needs fixing.

Welcome @Backup Gov18,

This is a documented issue.

Note: Only one active BarCodeScanner preview is supported currently. When using navigation, the best practice is to unmount any previously rendered BarCodeScanner component so the following screens can use without issues.

There is a workaround.

Instead of conditionally rendering the component, you could render it inside another dedicated screen component.

This way, after this new screen reads the barcode, you could navigate back to your first screen. Navigating back may unmount this new screen. You can force unmount if you need to.

As you are using react-navigation, you had better use .pop() instead of goBack().

You can also use expo-camera instead of expo-barcode-scanner. expo-camera does not have this issue. It also offers more options like flashlight/torch and switching cameras.

In functional component you don't need this keyword to read the props, actually props will pass as function argument. change your Home like this:

You must import only the components from the library, not the css or scss files. For example import ImageGallery from 'react-image-gallery' and use it below like as usual.

If it's not successful than try to import css/scss files to index.js