Maaz Zindani

Loading the index…

↑↓ move↵ openesc close4072 pages
Next.js and React

Formik touched stays empty even after the user visits a field

Errortouched 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.

  • Applies to Formik 2.4, React 19
  • Updated
  • By Maaz Zindani, Senior Software Engineer

Fix it fast

  1. 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>
  2. 2Match what you see, then jump to its fix

    1. 1touched stays {} while values change correctlyThe input never calls handleBlurFix
    2. 2The wrapped library input works but touched is empty only for itA custom component does not forward onBlurFix
    3. 3Server-prefilled or edit forms show no validation messagesFields were never visited but you expect errorsFix

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/*.jsx

2Fix

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 step

Confirmed by formik.org

Did this fix it?

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.jsx

2Fix

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 panel

Confirmed by formik.org

Did this fix it?

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 form

Confirmed by formik.org

Did this fix it?

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:

Related fixes

Next step

Want this handled for good?

I look after servers, apps and releases end to end. Tell me what keeps breaking.