Formik touched stays empty even after the user visits a field
touched is an empty object {}Short answer
Formik marks a field as touched on blur, not on change. If the input does not call handleBlur, or a custom component swallows onBlur, touched stays empty. Pass onBlur={handleBlur} to the real input, or call setFieldTouched yourself, or set initialTouched for a pre-visited form.
Fix it fast
1Find out which cause you have
Print touched and the values next to the form while you tab through the fields.
<pre>{JSON.stringify({ touched: formik.touched, errors: formik.errors }, null, 2)}</pre>2Match what you see, then jump to its fix
- 1
touched stays {} while values change correctlyThe input never calls handleBlurFix - 2
The wrapped library input works but touched is empty only for itA custom component does not forward onBlurFix - 3
Server-prefilled or edit forms show no validation messagesFields were never visited but you expect errorsFix
- 1
What does the error look like?
touched is an empty object {}Validation messages guarded by touched never appear
Cause 1 of 3
The input never calls handleBlur
1Check
Look at each input. onChange alone updates values but not touched.
grep -n "onBlur" src/components/*.jsx2Fix
Pass handleBlur to the input's onBlur, with a name that matches the field.
<input
name="email"
value={formik.values.email}
onChange={formik.handleChange}
onBlur={formik.handleBlur}
/>3Verify
Focus the field, then leave it. touched.email becomes true.
// watch the JSON panel from the first stepConfirmed by formik.org
Cause 2 of 3
A custom component does not forward onBlur
1Check
Open the wrapper (a UI library select, date picker or your own component) and confirm it forwards onBlur to the underlying element.
grep -rn "onBlur" src/components/Select.jsx2Fix
Forward onBlur, or call setFieldTouched from the wrapper's own blur event.
<Select
value={formik.values.role}
onChange={(v) => formik.setFieldValue("role", v)}
onBlur={() => formik.setFieldTouched("role", true)}
/>3Verify
touched.role is true after leaving the control.
// watch the JSON panelConfirmed by formik.org
Cause 3 of 3
Fields were never visited but you expect errors
1Check
Errors guarded by touched stay hidden until the field is visited.
grep -rn "touched\." src/2Fix
Set initialTouched for the fields that should show errors at once.
useFormik({
initialValues,
initialTouched: { email: true },
validate,
onSubmit,
});3Verify
The message appears on first render.
// reload the formConfirmed by formik.org
How do I stop it coming back?
- Write a small wrapper that always wires name, value, onChange and onBlur together.
- Show errors only when touched[field] and errors[field] are both set.
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
Formik onSubmit never runs when the form is submitted
The submit button stays disabled after the first click
Formik runs onSubmit only after validation finds no errors.
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 fixWeb apps
Astro Code component fails inside a React component
Astro components cannot be rendered directly via function call
Astro components such as Code only exist on the server and render static HTML.
2 causes, each with a fixWeb apps
React shows Attempted import error when importing a component or function
Attempted import error:
The build found the file but not the name you asked for.
2 causes, each with a fixWeb apps
How to catch and handle a 422 from Axios in a Redux thunk
action.error.message is 'Rejected' and action.payload is undefined
A 422 means the server read the request but cannot process its content, so repeating it unchanged fails again.
4 causes, each with a fixWeb apps
axios gets 429 Too Many Requests from a React app
429 (Too Many Requests)
A 429 comes from the server or an API gateway, not from axios: your client sent too many requests in a window.
4 causes, each with a fix