A component is changing an uncontrolled Autocomplete to be controlled

You ensured that the value property never had been undefined, but you had to do same for inputValue.

1. the "value" state with the value/onChange props combination. This state represents the value selected by the user, for instance when pressing Enter.
2. the "input value" state with the inputValue/onInputChange props combination. This state represents the value displayed in the textbox.

⚠️ These two state are isolated, they should be controlled independently.

Component becomes uncontrolled when inputValue property is undefined, and vice versa.

If in the following example you delete an empty string fromReact.useState('') you'll get the same error message because inputValue during first render is undefined.

import React from 'react'import TextField from '@material-ui/core/TextField'import Autocomplete from '@material-ui/lab/Autocomplete'const options = ['Option 1', 'Option 2']export default function AutocompleteLab() {  const [value, setValue] = React.useState(options[0])  const [inputValue, setInputValue] = React.useState('')  return (    <div>      <div>{`value: ${value !== null ? `'${value}'` : 'null'}`}</div>      <div>{`inputValue: '${inputValue}'`}</div>      <br />      <Autocomplete        value={value}        onChange={(_, newValue) => {          setValue(newValue)        }}        inputValue={inputValue}        onInputChange={(_, newInputValue) => {          setInputValue(newInputValue)        }}        options={options}        style={{ width: 300 }}        renderInput={(params) => <TextField {...params} label="Name" variant="outlined" />}      />    </div>  )}

I solved this by removing the default value.

             <Autocomplete                multiple                id="multiple-limit-tags"                options={(option) => option.label}                getOptionLabel={(option) => option}                // defaultValue={options || []}                renderInput={(params) => <TextField {...params} label="My Label" />}                         />

It wasn't obvious how to solve this, and the documentation doesn't help much either. I find it curious that a copy-pasted example from the documentation results in this error. I guess the example works because the choices are hard-coded.