react-native-router-flux navigates to default when a system dialog pops up in iOS

Created on 20 Feb 2019 · 6Comments · Source: aksonov/react-native-router-flux

Version

Expected behaviour

The user will stay on the current route (scene) when a system dialog pops up.

Actual behaviour

When a user accesses some features for the first time, like the camera, iOS will pop up a system dialog asking for permission to use the resource. When that dialog pops up, react-native-router-flux navigates to the default route. This is, of course, not desired.

Source

handoff

👍1

Most helpful comment

@MosesEsan @kamleshsindhal08 - I found a workaround. The problem is that the router component gets re-rendered, right? So in your router component class add this method:

class RouterComponent extends Component {
...
shouldComponentUpdate() { 
    return false;
} 
...
render() {
        return (
            <Router>
            ...
            </Router>
...

handoff on 6 Apr 2019

🚀1 ❤1 🎉1 😄1 👍1

All 6 comments

Damn... This one is dangerous!

pistonsky on 21 Feb 2019

👍1

Facing the same issue.. even when the keyboard pops up, navigated to the root scene!

kashanshah on 23 Feb 2019

@handoff Did you find a solution for this?

MosesEsan on 14 Mar 2019

Facing the same issue, any solution for both android and IOS

kamleshsindhal08 on 31 Mar 2019

@MosesEsan @kamleshsindhal08 - I found a workaround. The problem is that the router component gets re-rendered, right? So in your router component class add this method:

class RouterComponent extends Component {
...
shouldComponentUpdate() { 
    return false;
} 
...
render() {
        return (
            <Router>
            ...
            </Router>
...

handoff on 6 Apr 2019

🚀1 ❤1 🎉1 😄1 👍1

@MosesEsan @kamleshsindhal08 - I found a workaround. The problem is that the router component gets re-rendered, right? So in your router component class add this method:
class RouterComponent extends Component {
...
shouldComponentUpdate() { 
    return false;
} 
...
render() {
        return (
            <Router>
            ...
            </Router>
...

Many thanks. After two days of efforts, this solved the issue. Phew!