React history.push() is updating url but not navigating to it in browser
history.jsReact Router-V4history.js Problem Overview
I've read many things about react-router v4 and the npm history library to this point, but none seems to be helping me.
My code is functioning as expected up to the point when it should navigate and do a simple redirect when the url is changed using the history.push() method. The URL IS changing to the specified route, but not doing the redirect on the button push. Thanks in advance, still learning react-router...
I would like for the button push to do a simple redirect without the {forceRefresh:true}, which then reloads the whole page.
import React from 'react';
import createBrowserHistory from 'history/createBrowserHistory';
const history = createBrowserHistory({forceRefresh:true});
export default class Link extends React.Component {
onLogout() {
history.push("/signup");
}
render() {
return(
<div>
<h1>Your Links</h1>
<button onClick={this.onLogout.bind(this)}>Log Out</button>
</div>
)
}
}
history.js Solutions
Solution 1 - history.js
You shouldn't need to downgrade to v3, React-Router 4.0.0 is totally capable of accomplishing what the OP asked for.
const history = createBrowserHistory();
is a custom history object so you should use <Router>
to synchronize it with react-router instead of <BrowserRouter>
, which is what I assumed you were using.
Try this instead:
import React, {Component} from 'react';
import { Router } from 'react-router';
import { Route } from 'react-router-dom';
import createHistory from 'history/createBrowserHistory';
const history = createHistory();
class App extends Component {
constructor(props){
super(props);
}
render(){
return (
<Router history={history}> //pass in your custom history object
<Route exact path="/" component={Home} />
<Route path="/other" component={Other} />
<Router />
)
}
}
Once your custom history object is passed in via Router's history prop, history.push should work just as expected in anywhere of your app. (you might want to put your history object in a history config file and import it into places where you want to route programmatically).
For more info, see: React Router history object
Solution 2 - history.js
Check if you don't have nested BrowserRouter tags.
I had this issue on react-router v4 but I solved it after changing the app to only have the BrowserRouter at the top most level like the example below.
ReactDOM.render(
<BrowserRouter >
<App />
</BrowserRouter>,
document.getElementById('root')
);
Solution 3 - history.js
import Router
from react-router-dom
not BrowserRouter
// index.js
import React from "react";
import ReactDOM from "react-dom";
import App from "./App";
import { Router } from "react-router-dom";
import history from './utils/history'
ReactDOM.render(
<Router history={history}>
<App />
</Router>,
document.getElementById("root"));
serviceWorker.register();
// history.js
import { createBrowserHistory } from 'history';
export default createBrowserHistory();
on other components that you need to navigate import history and push
import History from '../utils/history'
History.push('/home')
Solution 4 - history.js
Rendering this would refresh on route change
`ReactDOM.render(
<AppContainer>
<BrowserRouter children={routes} basename={baseUrl} forceRefresh={true}/>
</AppContainer>,
document.getElementById("react-app")
);`
react-router-dom : 4.2.2
Solution 5 - history.js
Please ensure that you are using
const history = createBrowserHistory({forceRefresh:true});
not
const history = createBrowserHistory();
I was able to update the page once I added "{forceRefresh:true}"
Solution 6 - history.js
I have the same problem.
After some search i have found this react-router issue
I have currently downgrade react-router to the v3 and i use browserHistory
from the react-router
package and it's work fine.
Solution 7 - history.js
If you are using functional component then try to push using useHistory
Hook.
import React from 'react';
import { useHistory } from "react-router-dom";
export default function Link{
let history = useHistory();
onLogout() {
history.push("/signup");
}
return(
<div>
<h1>Your Links</h1>
<button onClick={this.onLogout.bind(this)}>Log Out</button>
</div>
)
}
Solution 8 - history.js
you can use
> forceRefresh={true}
in you code inside The BrowserRouter or inside Router
Solution 9 - history.js
in case somebody here with react-router-dom v6
I had the same problem and I had to downgrade to v5
and problem fixed.
Solution 10 - history.js
If you don't want to change router or version you could force the page to reload after updating history.
Eg:
history.push({
'pathname': '/signup',
'key': 'value'
})
document.location.reload()
Solution 11 - history.js
The feature is removed in react-router-dom v6. The best way would be to
- Create a state with default value of null and modify that state after async action, then
- Create an if statement inside of component that checks state and redirects.
- Add an dispatch action that resets the value of state to null