We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
I'm getting this error when I try to run the vanilla example in my own app
import NavigationBar from 'react-native-navbar' ... render () { const rightButtonConfig = { title: 'Next', handler: () => { alert('hello!') } } const titleConfig = { title: 'Hello, world', } return ( <View style={styles.overlayContainer}> <NavigationBar title={titleConfig} rightButton={rightButtonConfig} /> <View style={styles.topBar}> <Text>Dashboard Screen</Text> </View> </View> ) }
Has anyone seen this before?
The text was updated successfully, but these errors were encountered:
No idea, to be honest. Try to update all dependencies and reproduce it on a blank project.
Sorry, something went wrong.
I have this when I pass an empty string to a <Text>{emptyString}</Text> RN0.32
<Text>{emptyString}</Text>
Is it possible it's a cache of some sort? We were having this issue with RN 0.35 with a component that looked like this:
const MyComponent = ({title = ''}) => { return <Text style={styles.foo}>{title}</Text>; }
Which was throwing this error when title was getting defaulted to ''. Then we did this:
title
''
const MyComponent = ({title = ''}) => { return <Text>{title}</Text>; }
And it rendered just fine. Then, we returned it back to the first version, and it continued to render properly. For a few minutes, anyways.
FWIW, yet another question about displayName
displayName
https://stackoverflow.com/questions/50737684/displayname-property-in-react-native-cant-set-it-react-native-throws
No branches or pull requests
I'm getting this error when I try to run the vanilla example in my own app
Has anyone seen this before?
The text was updated successfully, but these errors were encountered: