Connected-react-router: Error `Could not find "store" in the context` when adding context to the provider and connectedRouter

[vchouhan]

Based on the migration to v5 and v6 and with the following code I'm getting the error listed below.

error message on application start
Could not find "store" in the context of "Connect(Home)". Either wrap the root component in a <Provider>, or pass a custom React context provider to <Provider> and the corresponding React context consumer to Connect(Home) in connect options.

Packages:
"connected-react-router": "^6.2.1", "react-redux": "^6.0.0"

[shieldo]

@vchouhan Just a check: did you restart your app after bumping your local package? I'd been getting the same error until I remembered I still needed to do that.

[cristian-sima]

Same here

[cristian-sima]

@vchouhan what font are you using?

[MateuszDev96]

+1

[Filipsi]

I am also having this problem, any updates on this?

[reisdev]

Same here!

[hgs-fredarters]

Same here.

[dagda1]

i have this problem with an ssr react project. i saw another problem where the props apppeared to be replaced altogether with the router props

[ArseniySilin]

Same here.

[draperunner]

Same here.

[BiosBoy]

Same problem. Any updates yet? :(

[BiosBoy]

I've solved it via bumping up to date all the packages linked with connected-react-router directly:
connected-react-router
react
redux
react-redux
react-router
react-router-dom

Seems like some of the inner dependencies had a problem with new connected-react-router context core.

And it works for me now! :)

[RyanPWalker]

Figured it out. All I was missing was the ReactReduxContext

import { Provider, ReactReduxContext } from 'react-redux';

render(
    <Provider store={store}>
        <ConnectedRouter history={history} context={ReactReduxContext}>
            <App />
        </ConnectedRouter>
    </Provider>,
    document.getElementById('root')
);

[crowmw]

Same here
@RyanPWalker and @BiosBoy does not help

@RyanPWalker I'm sorry

In my case, the problem concerned an outdated MaterialUI component that was creating Popovers outside the context. Changing the Popovers solved the problem.

[RyanPWalker]

@crowmw Why the thumbs down? It's still a valid solution, just not for your exact case.