The validation message never appears under an MUI X Date Picker
helperText is set on DatePicker but nothing renders under the fieldShort answer
A DatePicker does not take helperText or error as direct props. They belong to its inner TextField, so you pass them through slotProps.textField. With react-hook-form, wrap the picker in a Controller and feed error and helperText from fieldState, otherwise the form state never reaches the field.
Fix it fast
1Find out which cause you have
Check how your picker is registered. If it uses register() or has helperText as a direct prop, one of the causes below applies. Search the file for both.
grep -n "helperText\|renderInput\|register(" src/components/*.tsx2Match what you see, then jump to its fix
- 1
The picker renders, but no text appears below it, even with a hard-coded stringhelperText is a direct prop of DatePickerFix - 2
Props passed to renderInput are ignoredrenderInput was used, and it was removedFix - 3
The helper text works when hard-coded, but the validation message from the form never showsThe picker is not connected to the form stateFix
- 1
What does the error look like?
helperText is set on DatePicker but nothing renders under the fieldThe field never turns red after a failed validationPassing renderInput has no effect on the picker
Cause 1 of 3
helperText is a direct prop of DatePicker
1Check
In current MUI X, extra TextField props are not accepted on the picker itself. The docs say the textField slot is where custom props for the TextField go.
grep -n "<DatePicker" -A6 src/components/*.tsx2Fix
Move helperText into slotProps.textField.
<DatePicker
label="Start date"
slotProps={{ textField: { helperText: 'Please fill this field' } }}
/>3Verify
Reload the page. The text shows under the field.
npm run devConfirmed by mui.com
Cause 2 of 3
renderInput was used, and it was removed
1Check
The migration guide says renderInput was replaced by slot props. A leftover renderInput from an older tutorial is therefore dead code.
grep -rn "renderInput" src/2Fix
Delete renderInput and pass the TextField props, such as variant, through slotProps.textField.
<DatePicker
slotProps={{ textField: { variant: 'outlined', helperText: 'Required' } }}
/>3Verify
Run the type checker. An unknown renderInput prop would be reported if it is still there.
npx tsc --noEmitConfirmed by mui.com
Cause 3 of 3
The picker is not connected to the form state
1Check
react-hook-form gives the error to you in fieldState inside a Controller. If the picker is not inside a Controller, there is no fieldState to read.
grep -n "Controller" src/components/*.tsx2Fix
Wrap the picker in a Controller and pass fieldState.invalid and fieldState.error?.message to slotProps.textField. Give the rule a string message, otherwise there is no message to show.
<Controller
name="startDate"
control={control}
rules={{ required: 'Start date is required' }}
render={({ field, fieldState }) => (
<DatePicker
label="Start date"
value={field.value}
onChange={field.onChange}
slotProps={{
textField: {
onBlur: field.onBlur,
error: fieldState.invalid,
helperText: fieldState.error?.message,
},
}}
/>
)}
/>3Verify
Submit the form with the field empty. The text field turns red and shows the message.
npm run devConfirmed by react-hook-form.com
How do I stop it coming back?
- Set defaultValues for every field in useForm; an undefined starting value makes React warn about an uncontrolled field turning controlled.
- Give each validation rule a string message so the helper text has something to show.
- After a MUI X upgrade, read the migration guide for the picker before fixing symptoms one by one.
Sources
How was this page made?
I drafted this page with AI assistance from the official documents listed under Sources. Every cause above names the document that confirms it. I have not reproduced this fix on a machine of my own yet, so read it as documented guidance, not a test report. Found a mistake? Tell me.
Which stack is behind this page?
Projects of mine built on the same technologies:
- TaxiDexMy own multi-tenant taxi dispatch SaaS: API, dispatcher portal, driver and passenger apps, and the servers underneath.
- QistLockA NestJS and React SaaS driving an Android Device Owner agent that locks financed phones when payments lapse.
- TaskvareA task and project-management suite: React on the web, Flutter on mobile, TypeScript underneath.
Related fixes
Web apps
The renderInput prop stopped working on the MUI X DatePicker
The custom TextField (variant, size, helperText) is ignored
renderInput was removed from the MUI X date pickers in version 6.
3 causes, each with a fixWeb apps
React Hook Form: the submit button does nothing and onSubmit never runs
The page reloads when the form is submitted
handleSubmit runs your onSubmit only when validation passes.
4 causes, each with a fixWeb apps
React Hook Form isDirty does not go back to false
formState.isDirty is false after setValue
React Hook Form sets isDirty by comparing the current values with defaultValues.
4 causes, each with a fixWeb apps
react-hook-form: an optional number input gives NaN instead of a number or null
Validation fails on an optional numeric field
valueAsNumber returns NaN when a value cannot be converted, and setValueAs is ignored while valueAsNumber is on.
3 causes, each with a fixWeb apps
A Zod refinement error does not appear or does not clear in React Hook Form
The refinement error never shows until every other field is valid
Three Zod and React Hook Form rules explain it.
4 causes, each with a fixWeb apps
Module not found for antd/dist/antd.less after upgrading to Ant Design 5
Module not found: Error: Can't resolve 'antd/dist/antd.less'
Ant Design 5 dropped Less and the bundled CSS file for CSS-in-JS, so antd/dist/antd.less no longer exists.
3 causes, each with a fix