Repository navigation
form.reset during onSubmit ignores new default values #1681
Description
Describe the bug
The issue is that if you use the form's reset function from inside the form's onSubmit with new default values, they will be ignored.
This only happens if used in combination with form store-related watches such as "isDirty"
From the troubleshooting done by @LeCarbonator , it appears to be a race condition between handleSubmit and reset.
Your minimal, reproducible example
https://stackblitz.com/edit/vitejs-vite-jd2ttqqx?file=src%2FApp.tsx
Steps to reproduce
- Uncheck the checkbox.
- Click the Submit button
- See how the form goes back to the original default values instead of the new ones.
Expected behavior
Since we are calling the reset function with new values, those values should become the new form values.
How often does this bug happen?
Every time
Screenshots or Videos
No response
Platform
- OS: Any
- Browser: Any
- Node Version: 22
TanStack Form adapter
react-form
TanStack Form version
1.18.0
TypeScript version
v5.8.3
Additional context
A chat around this issue can be found here
Reacted by LeCarbonator, Rómulo Ochoa Valez, Jaime R., Gregor Billing, Jimmy Sunthornwutthikrai, Carl Bleick, Derek and Maxime
Activity
romulovalez commentedon Aug 18, 2025
+1, a workaround for now is to
setTimeout(() => form.reset());djordje-st commentedon Aug 19, 2025
Unfortunately that doesn't work for me either
dragonautdev commentedon Aug 19, 2025
@romulovalez @djordje-st The setTimeout strategy works, but the amount of time you need to wait varies.
when we discovered the issue, I had to set a timeout of up to 500ms for it to work.
LeCarbonator commentedon Aug 11, 2026
It looks like in v1, the check for new default values passed because
It therefore updated the default values.
isDirtywas just an immediate way to cause a rerender of the component, but anything would have done it, like unrelateduseStates.In v2, we have an equality check for both new default values as well as comparing your current state with the incoming values. This means that referential changes don't matter, but value changes do.
20260811-1840-38.5806507.mp4