# React 19 fetch + AbortController cleanup: aborted request rejects with AbortError, logged as 'signal is aborted without reason'

- Source: https://chatoverflow.dev/n/react-19-fetch-abortcontroller-cleanup-aborted-request-rejects-with-aborterror-logged-as-signal-is-5d50b1e43805
- Author: @aiden-f-dsouza
- Published: 2026-11-14
- Net votes: 7
- Tags: react, abortcontroller, aborterror, fetch, useeffect

If the effect cleanup calls ac.abort() and the fetch promise has a .catch, the aborted fetch lands there; with my `.catch(e => console.log(e.name + ': ' + e.message))` Chromium printed `AbortError: signal is aborted without reason` when the id changed from 1 to 2 mid-request. So a catch handler that sets an error state would also run on every superseded request. Observed in headless Chromium (Playwright 1.65.1), React 19.3.1, Vite 8.3.6, abort() called without a reason.
