React-navigation “you should only render one navigator warning” conflicts with React context
up vote
0
down vote
favorite
In my app I have a stacknavigator that renders a tabnavigator.
I want to share data between the tabs and for that I decided to use the Context API React provides.
let Tabs = createMaterialTopTabNavigator(
{
Info: (e: any) => <TabOne />,
Media: (e: any) => <TabTwo />,
}
)
If I export this and hand it to the stacknavigator everything is working fine. But when implementing the Context API with another class:
class ContextWrapper extends React.Component {
render() {
return (
<MyContext.Provider value={data}>
<Tabs />
</MyContext.Provider>
)
}
}
And hand this class to the stacknavigator I get this warning of
"you should only render one navigator "
The app still works this way, but I have this warning in the console.
I am aware of this page: https://reactnavigation.org/docs/en/common-mistakes.html and it's proposed solution of static router
but this way it gives me this error:
Cannot read property 'router' of undefined
Any on has a working solution for use with the Context API. Or any other way of sharing data between tabs?
react-native react-navigation
add a comment |
up vote
0
down vote
favorite
In my app I have a stacknavigator that renders a tabnavigator.
I want to share data between the tabs and for that I decided to use the Context API React provides.
let Tabs = createMaterialTopTabNavigator(
{
Info: (e: any) => <TabOne />,
Media: (e: any) => <TabTwo />,
}
)
If I export this and hand it to the stacknavigator everything is working fine. But when implementing the Context API with another class:
class ContextWrapper extends React.Component {
render() {
return (
<MyContext.Provider value={data}>
<Tabs />
</MyContext.Provider>
)
}
}
And hand this class to the stacknavigator I get this warning of
"you should only render one navigator "
The app still works this way, but I have this warning in the console.
I am aware of this page: https://reactnavigation.org/docs/en/common-mistakes.html and it's proposed solution of static router
but this way it gives me this error:
Cannot read property 'router' of undefined
Any on has a working solution for use with the Context API. Or any other way of sharing data between tabs?
react-native react-navigation
add a comment |
up vote
0
down vote
favorite
up vote
0
down vote
favorite
In my app I have a stacknavigator that renders a tabnavigator.
I want to share data between the tabs and for that I decided to use the Context API React provides.
let Tabs = createMaterialTopTabNavigator(
{
Info: (e: any) => <TabOne />,
Media: (e: any) => <TabTwo />,
}
)
If I export this and hand it to the stacknavigator everything is working fine. But when implementing the Context API with another class:
class ContextWrapper extends React.Component {
render() {
return (
<MyContext.Provider value={data}>
<Tabs />
</MyContext.Provider>
)
}
}
And hand this class to the stacknavigator I get this warning of
"you should only render one navigator "
The app still works this way, but I have this warning in the console.
I am aware of this page: https://reactnavigation.org/docs/en/common-mistakes.html and it's proposed solution of static router
but this way it gives me this error:
Cannot read property 'router' of undefined
Any on has a working solution for use with the Context API. Or any other way of sharing data between tabs?
react-native react-navigation
In my app I have a stacknavigator that renders a tabnavigator.
I want to share data between the tabs and for that I decided to use the Context API React provides.
let Tabs = createMaterialTopTabNavigator(
{
Info: (e: any) => <TabOne />,
Media: (e: any) => <TabTwo />,
}
)
If I export this and hand it to the stacknavigator everything is working fine. But when implementing the Context API with another class:
class ContextWrapper extends React.Component {
render() {
return (
<MyContext.Provider value={data}>
<Tabs />
</MyContext.Provider>
)
}
}
And hand this class to the stacknavigator I get this warning of
"you should only render one navigator "
The app still works this way, but I have this warning in the console.
I am aware of this page: https://reactnavigation.org/docs/en/common-mistakes.html and it's proposed solution of static router
but this way it gives me this error:
Cannot read property 'router' of undefined
Any on has a working solution for use with the Context API. Or any other way of sharing data between tabs?
react-native react-navigation
react-native react-navigation
asked Nov 10 at 17:59
marchello
5561724
5561724
add a comment |
add a comment |
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53241875%2freact-navigation-you-should-only-render-one-navigator-warning-conflicts-with-r%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown