React state still shows the old value right after setState
console.log(count) prints the old value right after setCount(count + 1)Short answer
A setter does not change the variable in the code that is running. State is a snapshot of one render, and calling the setter asks React to render again with a new value. Compute the next value in a local variable, use an updater function to chain updates, and use an effect to react after the render.
Fix it fast
1Find out which cause you have
Log the value in the handler and again in the component body. The body log shows the new value after the re-render, the handler log does not.
function handleClick() { setCount(count + 1); console.log('handler', count); } console.log('render', count);2Match what you see, then jump to its fix
What does the error look like?
console.log(count) prints the old value right after setCount(count + 1)three setCount(count + 1) calls raise the counter by 1, not 3
Cause 1 of 2
The handler reads the variable of its own render
1Check
The variable in a handler is fixed for that render. The setter only requests a new render, it does not change the variable.
// compare the 'handler' and 'render' logs from the first step2Fix
Work out the next value first, then use it for both the setter and the code that needs it.
function handleClick() {
const next = count + 1;
setCount(next);
console.log(next);
}3Verify
The log shows the new value and the screen updates on the next render.
// click once and read the consoleConfirmed by react.dev
Cause 2 of 2
Several updates in one handler use the same stale value
1Check
Each call is setCount(0 + 1) when count is 0 in that render, so every call queues the same value.
setCount(count + 1);
setCount(count + 1);
setCount(count + 1);2Fix
Pass an updater function. React runs the queued functions in order during the next render, and each gets the result of the previous one. Keep them pure.
setCount(c => c + 1);
setCount(c => c + 1);
setCount(c => c + 1);3Verify
One click now raises the counter by 3.
// click once and read the count on screenConfirmed by react.dev
How do I stop it coming back?
- Treat state variables as read-only values of the current render.
- Use the updater form whenever the new state depends on the old one.
- Keep logic that needs the committed state in the render body, not right after the setter.
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
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 fixWeb apps
Axios request is not cancelled when a React component unmounts
A cancelled request is logged as an error in the catch block
Axios cancels a request when you pass it an AbortSignal and later call abort() on its controller.
4 causes, each with a fix