[Solved]-A component is changing an uncontrolled input of type text to be controlled error in ReactJS-Reactjs

i am new to reactjs and i am using version 17 of reactjs i was getting this problem

i solved:

instead of this

const [email, setemail] = usestate();

i added this

const [email, setemail] = usestate("");

in usestate function i added quotes to initialize the data and the error was gone.

multiple approch can be applied:

• class based approch: use local state and define existing field with default value:

constructor(props) {
    super(props);
    this.state = {
      value:''
    }
  }
<input type='text'
                  name='firstname'
                  value={this.state.value}
                  classname="col-12"
                  onchange={this.onchange}
                  placeholder='enter first name' />

• using hooks react > 16.8 in functional style components:

[value, setvalue] = usestate('');
<input type='text'
                  name='firstname'
                  value={value}
                  classname="col-12"
                  onchange={this.onchange}
                  placeholder='enter first name' />

• if using proptypes and providing default value for proptypes in case of hoc component in functional style.

 hoc.proptypes = {
    value       : proptypes.string
  }
  hoc.efaultprops = {
    value: ''
  }

function hoc (){

  return (<input type='text'
                  name='firstname'
                  value={this.props.value}
                  classname="col-12"
                  onchange={this.onchange}
                  placeholder='enter first name' />)

}

change this

  const [values, setvalues] = usestate({intialstatevalues});

for this

  const [values, setvalues] = usestate(intialstatevalues);

if you're setting the value attribute to an object's property and want to be sure the property is not undefined, then you can combine the nullish coalescing operator ?? with an optional chaining operator ?. as follows:

<input
  value={myobject?.property ?? ''}
/>

i also faced the same issue. the solution in my case was i missed adding 'name' attribute to the element.

<div classname="col-12">
   <label htmlfor="username" classname="form-label">username</label>
        <div classname="input-group has-validation">
             <span classname="input-group-text">@</span>
                  <input 
                      type="text" 
                      classname="form-control" 
                      id="username"
                      placeholder="username" 
                      required=""
                      value={values.username}
                      onchange={handlechange}
                  />
                  <div classname="invalid-feedback">
                      your username is required.
                  </div>
        </div>
</div>

after i introduced name = username in the input list of attributes it worked fine.

for functional component:

const signin = () => {

  const [formdata, setformdata] = usestate({
    email: "",
    password: ""
  });

  
  const handlechange = (event) => {
    const { value, name } = event.target;
    setformdata({...formdata, [name]: value });
  };


  const handlesubmit = (e) => {
    e.preventdefault();
    console.log("signed in");
    setformdata({
      email: "",
      password: ""
    });
  };


  return (
    <div classname="sign-in-container">
      <form onsubmit={handlesubmit}>
        <forminput
          name="email"
          type="email"
          value={formdata.email}
          handlechange={handlechange}
          label="email"
          required
        />
        <forminput
          name="password"
          type="password"
          value={formdata.password}
          handlechange={handlechange}
          label="password"
          required
        />
        <custombutton type="submit">sign in</custombutton>
      </form>
    </div>
  );
};

export default signin;

while this might sound crazy, the thing that fixed this issue for me was to add an extra div. a portion of the code as an example:

  ... [other code] ...
  const [brokerlink, setbrokerlink] = usestate('');
  ... [other code] ...

  return (
    ... [other code] ...
              <div stylename="advanced-form" style={{ margin: '0 auto', }}>
                {/* note: this div */}
                <div>
                  <div stylename="form-field">
                    <div>broker link</div>
                    <input
                      type="text"
                      name="brokerlink"
                      value={brokerlink}
                      placeholder=""
                      onchange={e => setbrokerlink(e.target.value)}
                    />
                  </div>
                </div>
              </div>
    ... [other code] ...
  );
... [other code] ...

was very strange. without this extra div, it seems react initially rendered the input element with no value attribute but with an empty style attribute for some reason. you could see that by looking at the html. and this led to the console warning..

what was even weirder was that adding a default value that is not an empty string or doing something like value={brokerlink || ''} would result in the exact same problem..

another weird thing was i had 30 other elements that were almost exactly the same but did not cause this problem. only difference was this brokerlink one did not have that outer div.. and moving it to other parts of the code without changing anything removed the warning for some reason..

probably close to impossible to replicate without my exact code. if this is not a bug in react or something, i don't know what is.

in my case it was pretty much what mayank shukla's top answer says. the only detail was that my state was lacking completely the property i was defining.

for example, if you have this state:

state = {
    "a" : "a",
    "b" : "b",
}

if you're expanding your code, you might want to add a new prop so, someplace else in your code you might create a new property c whose value is not only undefined on the component's state but the property itself is undefined.

to solve this just make sure to add c into your state and give it a proper initial value.

e.g.,

state = {
    "a" : "a",
    "b" : "b",
    "c" : "c", // added and initialized property!
}

hope i was able to explain my edge case.

warning: a component is changing an uncontrolled input of type text to be controlled. input elements should not switch from uncontrolled to controlled (or vice versa). decide between using a controlled or uncontrolled input element for the lifetime of the component.

solution : check if value is not undefined

react / formik / bootstrap / typescript

example :

{ values?.purchaseobligation.remainingyear ?
  <input
   tag={field}
   name="purchaseobligation.remainingyear"
   type="text"
   component="input"
  /> : null
}

the reason of this problem when input field value is undefined then throw the warning from react. if you create one changehandler for multiple input field and you want to change state with changehandler then you need to assign previous value using by spread operator. as like my code here.

constructor(props){
    super(props)
    this.state = {
        user:{
            email:'',
            password:''
        }
    }
}

// this handler work for every input field
changehandler = event=>{
    // dynamically update state when change input value
    this.setstate({
        user:{
            ...this.state.user,
            [event.target.name]:event.target.value
        }
    })
}

submithandler = event=>{
    event.preventdefault()

    // your code here...
}

render(){
    return (
        <div classname="mt-5">
       
            <form onsubmit={this.submithandler}>
                <input type="text" value={this.state.user.email} name="email" onchage={this.changehandler} />
                
                <input type="password" value={this.state.user.password} name="password" onchage={this.changehandler} />

                <button type="submit">login</button>
            </form>
      

        </div>
    )
}

like this

value={this.state.fields && this.state.fields["name"] || ''}

work for me.

but i set initial state like this:

this.state = {
  fields: [],
}

if you use multiple input in on field, follow: for example:

class adduser extends react.component {
   constructor(props){
     super(props);

     this.state = {
       fields: { username: '', password: '' }
     };
   }

   onchangefield = event => {
    let name = event.target.name;
    let value = event.target.value;
    this.setstate(prevstate => {
        prevstate.fields[name] =  value;
        return {
           fields: prevstate.fields
        };
    });
  };

  render() { 
     const { username, password } = this.state.fields;
     return (
         <form>
             <div>
                 <label htmlfor="username">username</label>
                 <input type="text" 
                        id='username' 
                        name='username'
                        value={username}
                        onchange={this.onchangefield}/>
              </div>
              <div>
                  <label htmlfor="password">password</label>
                  <input type="password" 
                         id='password' 
                         name='password'
                         value={password}
                         onchange={this.onchangefield}/>
              </div>
         </form>
     ); 
  }
}

search your problem at:

onchangefield = event => {
    let name = event.target.name;
    let value = event.target.value;
    this.setstate(prevstate => {
        prevstate.fields[name] =  value;
        return {
            fields: prevstate.fields
        };
    });
};

using react hooks also don't forget to set the initial value.
i was using <input type='datetime-local' value={eventstart} /> and initial eventstart was like

const [eventstart, seteventstart] = usestate();
instead
const [eventstart, seteventstart] = usestate('');.

the empty string in parentheses is difference.
also, if you reset form after submit like i do, again you need to set it to empty string, not just to empty parentheses.

this is just my small contribution to this topic, maybe it will help someone.

i came across the same warning using react hooks, although i had already initialized the initial state before as:-

const [post,setpost] = usestate({title:"",body:""})

but later i was overriding a part of the predefined state object on the onchange event handler,

 const onchange=(e)=>{
        setpost({[e.target.name]:e.target.value})
    }

solution i solved this by coping first the whole object of the previous state(by using spread operators) then editing on top of it,

 const onchange=(e)=>{
        setpost({...post,[e.target.name]:e.target.value})
    }

put empty value if the value does not exist or null.

value={ this.state.value || "" }

best way to fix this is to set the initial state to ''.

constructor(props) {
 super(props)
  this.state = {
    fields: {
      first_name: ''
    }
  }
  this.onchange = this.onchange.bind(this);
}

onchange(e) {
  this.setstate({
    fields:{
     ...this.state.fields,
     [e.target.name]: e.target.value
    }
  })
}


render() {
  return(
    <div classname="form-group">
      <input
        value={this.state.fields.first_name}
        onchange={this.onchange}
        classname="form-control"
        name="first_name" // same as state key
        type="text"
        refs="name"
        placeholder="name *"
      />
      <span style={{color: "red"}}>{this.state.errors.first_name}</span>
    </div>
  )
} 

then you can still run your checks like if (field) and still achieve the same result if you have the value as ''.

now since your value is now classified as type string instead of undefined after evaluation. thus, clearing the error from the console of a big red block 😁😎.

set current state first ...this.state

its because when you are going to assign a new state it may be undefined. so it will be fixed by setting state extracting current state also

this.setstate({...this.state, field})

if there is an object in your state, you should set state as follows, suppose you have to set username inside the user object.

this.setstate({user:{...this.state.user, ['username']: username}})

that's happen because the value can not be undefined or null to resolve you can do it like this

value={ this.state.value ?? "" }

as mentioned above you need to set the initial state, in my case i forgot to add ' ' quotes inside setsate();

  const adduser = (props) => {
  const [enteredusername, setenteredusername] = usestate()
  const [enteredage, setenteredage] = usestate()

gives the following error

correct code is to simply set the initial state to an empty string ' '

  const adduser = (props) => {
  const [enteredusername, setenteredusername] = usestate('')
  const [enteredage, setenteredage] = usestate('')

const [name, setname] = usestate()

generates error as soon as you type in the text field

const [name, setname] = usestate('') // <-- by putting in quotes 

will fix the issue on this string example.

simply, you must set initial state first

if you don't set initial state react will treat that as an uncontrolled component

in addition to the accepted answer, if you're using an input of type checkbox or radio, i've found i need to null/undefined check the checked attribute as well.

<input
  id={myid}
  name={myname}
  type="checkbox" // or "radio"
  value={mystatevalue || ''}
  checked={someboolean ? someboolean : false}
  />

and if you're using ts (or babel), you could use nullish coalescing instead of the logical or operator:

value={mystatevalue ?? ''}
checked={someboolean ?? false}

inside the component put the input box in the following way.

<input classname="class-name"
              type= "text"
              id="id-123"
              value={ this.state.value || "" }
              name="field-name"
              placeholder="enter name"
              />

changing value to defaultvalue will resolve it.

note:

defaultvalue is only for the initial load. if you want to initialize the input then you should use defaultvalue, but if you want to use state to change the value then you need to use value. read this for more.

i used value={this.state.input ||""} in input to get rid of that warning.