-
Notifications
You must be signed in to change notification settings - Fork 24.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[NavigatorIOS] SetState does not rerender NavigatorIOS component (w/ example repo) #1403
Comments
I suspect you're running into the same issue I did (though I wanted to change the initial routes). #1300 I believe re-rendering the navigator is a no-go for the time being. @ericvicenti thoughts? |
The reason this isn't happening is that this property is only applied on |
@the4dpatrick - this commit on your project fixes the problem, but I think it's a little hacky. If you want to clean it up into a nicer solution that would be great. Feel free to clone that repo and try it - I included the |
This is a dup of #846 |
* Approach borrowed from: facebook#1403 (comment) * Would need to follow similar pattern to update other navigation / nav bar props on resetTo / replace, but want to limit the changes from RN master for now.
* Approach borrowed from: facebook#1403 (comment) * Would need to follow similar pattern to update other navigation / nav bar props on resetTo / replace, but want to limit the changes from RN master for now.
* Approach borrowed from: facebook#1403 (comment) * Would need to follow similar pattern to update other navigation / nav bar props on resetTo / replace, but want to limit the changes from RN master for now.
* Approach borrowed from: facebook#1403 (comment) * Would need to follow similar pattern to update other navigation / nav bar props on resetTo / replace, but want to limit the changes from RN master for now.
* Approach borrowed from: facebook#1403 (comment) * Would need to follow similar pattern to update other navigation / nav bar props on resetTo / replace, but want to limit the changes from RN master for now.
* Approach borrowed from: facebook#1403 (comment) * Would need to follow similar pattern to update other navigation / nav bar props on resetTo / replace, but want to limit the changes from RN master for now.
* Approach borrowed from: facebook#1403 (comment) * Would need to follow similar pattern to update other navigation / nav bar props on resetTo / replace, but want to limit the changes from RN master for now.
* Approach borrowed from: facebook#1403 (comment) * Would need to follow similar pattern to update other navigation / nav bar props on resetTo / replace, but want to limit the changes from RN master for now.
* Approach borrowed from: facebook#1403 (comment) * Would need to follow similar pattern to update other navigation / nav bar props on resetTo / replace, but want to limit the changes from RN master for now.
* Approach borrowed from: facebook#1403 (comment) * Would need to follow similar pattern to update other navigation / nav bar props on resetTo / replace, but want to limit the changes from RN master for now.
* Approach borrowed from: facebook#1403 (comment) * Would need to follow similar pattern to update other navigation / nav bar props on resetTo / replace, but want to limit the changes from RN master for now.
Here is a repo showing the bug https://github.com/the4dpatrick/react-native-bug-example
I am trying to toggle NavigatorIOS on and off based on the prop
navigationBarHidden
set to a state value.I pass along a method to child components that passes the parent's context and toggle the state value.
Inside the sidemenu, I am calling
this.props.toggleNavigation()
onPress. This correctly toggles the navbar when initially hidden, but when you pressonLeftButtonPress
, the navbar does not toggle off.Here is the start of the IRC chat on this bug https://botbot.me/freenode/reactnative/2015-05-26/?msg=40122019&page=1
The text was updated successfully, but these errors were encountered: