Skip to content
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

react.children.only expected to receive a single reactelement child #14625

Closed
lenmoyouziJiangjun opened this issue Jun 20, 2017 · 2 comments
Closed
Labels
Resolution: Locked This issue was locked by the bot.

Comments

@lenmoyouziJiangjun
Copy link

lenmoyouziJiangjun commented Jun 20, 2017

`var Main = React.createClass({
getInitialState(){
return {
selectTab: 0,
}
},
render(){
return (

<TabBarIOS.Item
title="home"
icon={{uri: 'tabbar_home', scale: 2}}
onPress={()=>this.tabBarClick(0)}
selected={this.state.selectTab===0}
>

            </TabBarIOS.Item>
            <TabBarIOS.Item
                title="discover"
                icon={{uri: 'tabbar_discover', scale: 2}}
                onPress={()=>this.tabBarClick(1)}
                selected={this.state.selectTab===1}
            >

            </TabBarIOS.Item>
   </TabBarIOS>
    [)](url)
},

tabBarClick(index){
    this.setState({
        selectTab: index,
    })
}

}); · when I delete selected={this.state.selectTab===0} its ok 。
`

@ItsNoHax
Copy link

ItsNoHax commented Jun 23, 2017

Somewhere in one of your component's render method you have:
(Doesn't have to be a 'View' component exact but you get the picture)

<View>
</View>
<View>
</View>

Where you should only have 1 parent view:

<View>
    <View>
    </View>
<View>

@hramos
Copy link
Contributor

hramos commented Aug 24, 2017

Hi there! This issue is being closed because it has been inactive for a while. Maybe the issue has been fixed in a recent release, or perhaps it is not affecting a lot of people. Either way, we're automatically closing issues after a period of inactivity. Please do not take it personally!

If you think this issue should definitely remain open, please let us know. The following information is helpful when it comes to determining if the issue should be re-opened:

  • Does the issue still reproduce on the latest release candidate? Post a comment with the version you tested.
  • If so, is there any information missing from the bug report? Post a comment with all the information required by the issue template.
  • Is there a pull request that addresses this issue? Post a comment with the PR number so we can follow up.

If you would like to work on a patch to fix the issue, contributions are very welcome! Read through the contribution guide, and feel free to hop into #react-native if you need help planning your contribution.

@hramos hramos added the Icebox label Aug 24, 2017
@hramos hramos closed this as completed Aug 24, 2017
@facebook facebook locked as resolved and limited conversation to collaborators Aug 24, 2018
@react-native-bot react-native-bot added the Resolution: Locked This issue was locked by the bot. label Aug 24, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Resolution: Locked This issue was locked by the bot.
Projects
None yet
Development

No branches or pull requests

5 participants
@hramos @ItsNoHax @lenmoyouziJiangjun @react-native-bot and others