Redux don't update component in dev env

[Borrelli]

🐛 Bug Report

Environment

Expo CLI 2.13.0 environment info:
System:
OS: Windows 10
Binaries:
npm: 6.4.1 - C:\Program Files\nodejs\npm.CMD

//package.json
  "dependencies": {
    "expo": "^32.0.6",
    "react": "^16.8.3",
    "react-native": "https://github.com/expo/react-native/archive/sdk-32.0.1.tar.gz",
    "react-native-elevated-view": "0.0.6",
    "react-native-gesture-handler": "^1.1.0",
    "react-native-paper": "^2.12.0",
    "react-native-responsive-dimensions": "^2.0.1",
    "react-navigation": "^2.0.1",
    "react-navigation-material-bottom-tabs": "^0.4.0",
    "react-redux": "^6.0.1",
    "redux": "^4.0.1"
  },

Steps to Reproduce

Doing a mapStateToProps with a console.log for checking if component is updating with new props when dispatch.

const mapStateToProps = (state) => {
console.log("props updating")
    return {
        card: state.cardHandler.card
    }
}
export default connect(mapStateToProps)(Item)

You can see this issue for more information and reproducing

https://stackoverflow.com/questions/55315191/connect-doesnt-refresh-when-state-change-on-react-native-with-redux/

Expected Behavior

Component with connect() should reload on store modification

Actual Behavior

Nothing happened on developpement mode, but if env is production, redux working and component update.

//settings.json
{
  "hostType": "lan",
  "lanType": "ip",
  "dev": true, //working with false
  "minify": false,
  "urlRandomness": "53-g5j"
}

[AdamJNavarro]

Hey @Borrelli,

Before we investigate this, as I suspect it may not be Expo-related, can you try reproducing this issue in a vanilla React Native project and seeing if it still persists? If it works properly then please create a Snack with just the minimal code and dependencies required to reproduce the issue so we can debug on our end.

Cheers,
Adam

[Borrelli]

Please, can you explain me what you mean by "reproducing this issue in a vanilla React Native project".
is it related to https://www.npmjs.com/package/react-native-vanilla ?

[AdamJNavarro]

Yes, sorry for the confusion. The phrase vanilla react native most often means a plain react-native project. You'll want to follow the React Native CLI Quickstart guide here.

[Borrelli]

I put the projet on snack and there is it:
https://snack.expo.io/@borrelli/measy

You can check bug on clicking an item, and click on "AJOUTER AU PANIER", the store work, you can see a text add and delete.

But if i run it on android emulator or expo cli with device on developpement mode. This shield don't add and delete. The store don't update the component...

[Borrelli]

I solved the problem by completely reinstalling the application. Probably a problem of incompatibility...

[adamsythe]

I have this issue accross all 3 computers that run my app. I have tried uninstalling and reinstalling

[HenriBrg]

Me too, still stuck with component which is not rendered in development environment, but it works in production mode of Expo

[josharrowsmith]

great spot, ive been stuck on this for 4 hours. please fix

[Borrelli]

Me too, still stuck with component which is not rendered in development environment, but it works in production mode of Expo

Do you try a clean reinstallation?

[adamsythe]

Me too, still stuck with component which is not rendered in development environment, but it works in production mode of Expo

Do you try a clean reinstallation?

I have this problem with all 3 computers i use for development, each one when i started development i installed expo and pulled the project from scratch

[msevestre]

Do you have some special code initialization that is only happening when DEV is true or something like this? This could explain why your code only works in production

[adamsythe]

Not as far as I can tell

[Borrelli]

@msevestre @adamsythe the DEV env is handling by expo. It should be write on the official doc ...

[msevestre]

@Borrelli @adamsythe
__DEV__ is true in development. THis allows you to add specific middleware such as redux-logger or REDUX_DEV_TOOLS etc.

The bug description strongly suggests that something is happening to the redux middleware in dev mode that is breaking redux. This actually has nothing to do with expo

[adamsythe]

here are my dev dependencies
"devDependencies": {
"babel-preset-expo": "^5.0.0",
"eslint": "^5.8.0",
"eslint-config-airbnb": "^17.1.0",
"eslint-config-rallycoding": "^3.2.0",
"eslint-config-standard": "^12.0.0",
"eslint-plugin-import": "^2.14.0",
"eslint-plugin-jsx-a11y": "^6.1.2",
"eslint-plugin-node": "^8.0.0",
"eslint-plugin-promise": "^4.0.1",
"eslint-plugin-react": "^7.11.1",
"eslint-plugin-react-native": "^3.5.0",
"eslint-plugin-standard": "^4.0.0",
"husky": "^1.1.3",
"lint-staged": "^8.0.4",
"schedule": "^0.4.0"
}

[bellini666]

I think I'm suffering from this issue in SDK 33 but the other way around.

Upgrading to react-redux 7 was not possible since it broke a few things. Keeping react-redux 6 (the same that I was using in SDK 32) is working, but redux only updates my components in development mode. In production mode it will not update.