aksonov / react-native-router-flux

The first declarative React Native router
MIT License
8.98k stars 2.11k forks source link

4.2.0 → 4.3.0: TypeError: navigationStore.getStateForAction is not a function. #3746

Open allenmanning opened 3 years ago

allenmanning commented 3 years ago

Version

Expected behaviour

No component exception, similar to 4.2.0.

Actual behaviour

With upgrade to 4.2.0 → 4.3.0

TypeError: navigationStore.getStateForAction is not a function. (In 'navigationStore.getStateForAction(action, state)', 'navigationStore.getStateForAction' is undefined)

This similar ticket, didn't help me resolve this: https://github.com/aksonov/react-native-router-flux/issues/3294

My router:


  const defaultReducer = new Reducer(params);
  return (state, action) => {
    return defaultReducer(state, action);
  };
};

class Routes extends React.Component {

  render() {
    return (
      <Router createReducer={reducerCreate} scenes={scenes} />
    );
  }
}

Routes.propTypes = {
  dispatch: PropTypes.func,
};

export default connect()(Routes);
aksonov commented 3 years ago

Could you reproduce it with react-native/Example or custom fork of it?

ahsan-abrar commented 3 years ago

"react": "17.0.1", "react-native": "0.64.0", "react-native-router-flux": "^4.2.0",

Screenshot_1617913852

ahsan-abrar commented 3 years ago

here is a quick fix, downgrade react-native-router-flux to react-native-router-flux": "4.0.0-beta.27" and run these commands

watchman watch-del-all yarn cache clean --force npm cache clean --force # optional - in case you also have used npm rm -rf node_modules/ rm yarn.lock rm package-lock.json # optional - in case you also have used npm rm -rf $TMPDIR/metro- rm -rf $TMPDIR/haste- yarn yarn start --reset-cache

reference: https://github.com/aksonov/react-native-router-flux/issues/3023

nica0012 commented 3 years ago

I am having the same issue, I am trying to get currentscene, so I did redux implementation this same way - the example redux integration doesn't make much sense with everything in app.js, it is very confusing. is there another way to fix this besides downgrading? I have already made significant changes to my whole app because of 4.3.1.

Sargnec commented 3 years ago

I'm facing this issue also. Upgraded to 4.3.1 because of iphone 12 bottom bar have problem and I saw that issue fixed at 4.3.1 now I'm here

HessiPard commented 3 years ago

have this problem too after upgrade 4.2 => 4.3.1

allenmanning commented 3 years ago

Is this project being maintained? @aksonov There are many folks running into this.

ahsan-abrar commented 3 years ago

Is this project being maintained? @aksonov There are many folks running into this.

I think the package was not being maintained, I simply moved to react-navigation

ekoooo commented 3 years ago

same issues

wg-d commented 2 years ago

I am having exactly same issue with react-native-router-flux. I followed @ahsan-abrar , but the issue still persists.