AbortSignal/AbortController doesn't work

[lufinkey]

Description

• AbortController / AbortSignal are used in javascript to cancel a request started with fetch, or any other async task that should be cancellable (docs here)
• In react native, there are several issues with these APIs:
  • DOMException, which is thrown when AbortController is used, doesn't actually exist as a type
  • Calling abortController.abort() doesn't actually have any effect, and abortSignal.reason is undefined.
  • abortSignal.throwIfAborted() doesn't exist as a function
  • I haven't fully verified this, but it looks like AbortController doesn't actually fully abort fetch requests.

Steps to reproduce

• Use javascript AbortController the way it's documented here

React Native Version

0.76.1

Affected Platforms

Runtime - Android, Runtime - iOS

Output of npx @react-native-community/cli info

System:
  OS: macOS 15.3.1
  CPU: (14) arm64 Apple M4 Max
  Memory: 175.34 MB / 36.00 GB
  Shell:
    version: "5.9"
    path: /bin/zsh
Binaries:
  Node:
    version: 22.14.0
    path: ~/.nvm/versions/node/v22.14.0/bin/node
  Yarn:
    version: 1.22.22
    path: ~/.nvm/versions/node/v22.14.0/bin/yarn
  npm:
    version: 10.9.2
    path: ~/.nvm/versions/node/v22.14.0/bin/npm
  Watchman: Not Found
Managers:
  CocoaPods:
    version: 1.16.2
    path: /Users/luisfinke/.rvm/gems/ruby-3.2.0/bin/pod
SDKs:
  iOS SDK:
    Platforms:
      - DriverKit 24.2
      - iOS 18.2
      - macOS 15.2
      - tvOS 18.2
      - visionOS 2.2
      - watchOS 11.2
  Android SDK: Not Found
IDEs:
  Android Studio: 2024.2 AI-242.23726.103.2422.13103373
  Xcode:
    version: 16.2/16C5032a
    path: /usr/bin/xcodebuild
Languages:
  Java:
    version: 23.0.1
    path: /usr/bin/javac
  Ruby:
    version: 3.2.0
    path: /Users/luisfinke/.rvm/rubies/ruby-3.2.0/bin/ruby
npmPackages:
  "@react-native-community/cli": Not Found
  react:
    installed: 18.3.1
    wanted: 18.3.1
  react-native:
    installed: 0.76.1
    wanted: 0.76.1
  react-native-macos: Not Found
npmGlobalPackages:
  "*react-native*": Not Found
Android:
  hermesEnabled: Not found
  newArchEnabled: Not found
iOS:
  hermesEnabled: Not found
  newArchEnabled: Not found

Stacktrace or Logs

N/A

Reproducer

N/A

Screenshots and Videos

No response

[react-native-bot]

Tip

Newer version available: You are on a supported minor version, but it looks like there's a newer patch available - 0.76.7. Please upgrade to the highest patch for your minor or latest and verify if the issue persists (alternatively, create a new project and repro the issue in it). If it does not repro, please let us know so we can close out this issue. This helps us ensure we are looking at issues that still exist in the most recent releases.

[react-native-bot]

Tip

Newer version available: You are on a supported minor version, but it looks like there's a newer patch available - undefined. Please upgrade to the highest patch for your minor or latest and verify if the issue persists (alternatively, create a new project and repro the issue in it). If it does not repro, please let us know so we can close out this issue. This helps us ensure we are looking at issues that still exist in the most recent releases.

[react-native-bot]

Warning

Missing reproducer: We could not detect a reproducible example in your issue report. Please provide either:

• If your bug is UI related: a Snack
• If your bug is build/upgrade related: a project using our Reproducer Template
• Otherwise send us a Pull Request with the RNTesterPlayground.js edited to reproduce your bug.

[migueldaipre]

Hey @lufinkey, Can you add the minimum reproducer using our Reproducer Template?

[sandeepeven]

Hey @lufinkey, I checked with the Reproducer Template mentioned above Thanks to @migueldaipre . Abort controller worked in my case. You can use the same template to create a reproducible so that it would be easier to target the issue first.

[lufinkey]

Gotcha, I'll try to put together a reproduction later today if I have time

…

On Mon, Mar 17, 2025, 1:01 AM Sandeep Singh ***@***.***> wrote: Hey @lufinkey <https://github.com/lufinkey>, I checked with the Reproducer Template mentioned above Thanks to @migueldaipre <https://github.com/migueldaipre> . Abort controller worked in my case <https://github.com/sandeepeven/react-native-issue-abort-controller>. You can use the same template to create a reproducible so that it would be easier to target the issue first. — Reply to this email directly, view it on GitHub <#50015 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AB3VGUIB22OWEQAO2WMIIAT2UZJKXAVCNFSM6AAAAABY6TQ77KVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDOMRYGE2TONBYG4> . You are receiving this because you were mentioned.Message ID: ***@***.***> [image: sandeepeven]*sandeepeven* left a comment (facebook/react-native#50015) <#50015 (comment)> Hey @lufinkey <https://github.com/lufinkey>, I checked with the Reproducer Template mentioned above Thanks to @migueldaipre <https://github.com/migueldaipre> . Abort controller worked in my case <https://github.com/sandeepeven/react-native-issue-abort-controller>. You can use the same template to create a reproducible so that it would be easier to target the issue first. — Reply to this email directly, view it on GitHub <#50015 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AB3VGUIB22OWEQAO2WMIIAT2UZJKXAVCNFSM6AAAAABY6TQ77KVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDOMRYGE2TONBYG4> . You are receiving this because you were mentioned.Message ID: ***@***.***>