[TextInput] Not clear what Warning Message for TextInput means.

[alinz]

After upgrading React Native to 0.6.0 I'm starting to get this warning.

Warning: Don't set .props.style of the React component <TextInput />. Instead, specify the correct value when initially creating the element or use React.cloneElement to make a new element with updated props.

I did everything as it describes above. but nothing works so far. Any idea why this warning start to show up. I would like to see some example if that possible,

[brentvatne]

Can you show us some code that produces this warning?

[alinz]

Well, I'm using my fork version of react-native which can be found here.
I have only changes 2 things

• added es6.modules to white list here
• force the version to be 0.5.0 to by pass some npm errors.

now the regular TextInput component keeps sending me that warning. I'm not doing any fancy thing. It used to work but changes to latest code causes this warning.

I needed the new version react-native because it has new methods for fixing this issue #1402

[brentvatne]

We can't really support forks, but if you can reproduce this on a standard build of React Native then please do link to the repo and I'll be happy to take a look! Closing until then

[jawadrehman]

@brentvatne I use the version 0.6-rc and I can see the same warning message.

[admmasters]

This is occurring on the 0.6.0 release version. Can be reproduced by creating a brand new project and adding at least one TextInput field to the render method.

[admmasters]

This is related to line 422 of TextInput.js:

props.style = [styles.input, this.props.style]

You are mutating props within the render method - which obviously is not good practice.

[ide]

@admmasters do you want to submit a PR? Cloning the props should fix it ex:

var props = {
   ...this.props,
  style: [styles.input, this.props.style],
};

[admmasters]

Sure - I was just looking at it now :)

[alinz]

👍

[chirag04]

saw this warning today.

[chirag04]

@ide Is this merged in master? I just updated to 0.7.1 and i still see this warning

[ide]

It has not been merged.

[browniefed]

@brentvatne looks like the solution got merged 5 days ago.

[brentvatne]

@browniefed - indeed, this is in master now! Thanks for pointing it out 😄