Change Details

See context in [ENG-2288](https://linear.app/comm/issue/ENG-2288/reconsider-persistorflush-call-in-nativereduxredux-setupjs). `redux-persist` doesn't wait for `REHYDRATE` if you call `persistor.flush` directly, which can result in data being overriden.

Originally, this diff was just making sure that the `dispatch` didn't occur before `REHYDRATE`. But when testing that change I found that calling `dispatch` from a reducer triggered an error. More context in [this comment](https://phab.comm.dev/D5672#169056), but this diff is now just removing the `dispatch`, with the expectation that the error-handling functionality here will be improved following the work in [ENG-1974](https://linear.app/comm/issue/ENG-1974/analysis-of-errors-in-sqlitequeryexecutor).

See context in [ENG-2288](https://linear.app/comm/issue/ENG-2288/reconsider-persistorflush-call-in-nativereduxredux-setupjs)Originally, this diff was just making sure that the `dispatch` didn't occur before `REHYDRATE`. But when testing that change I found that calling `dispatch` from a reducer triggered an error. `redux-persist` doesn't wait for `REHYDRATE` if you call `persistor.flush` directlyMore context in [this comment](https://phab.comm.dev/D5672#169056), but this diff is now just removing the `dispatch`, which can result in data being overridenith the expectation that the error-handling functionality here will be improved following the work in [ENG-1974](https://linear.app/comm/issue/ENG-1974/analysis-of-errors-in-sqlitequeryexecutor).