[bug] resetApiState() triggers AbortController Illegal invocation when used with a retry() wrap in RTKQ in v2.9.2+

[AndreaCuneo]

Upgrading from v2.9.1 to v2.10.1 cause error "Failed to execute 'abort' on 'AbortController': Illegal invocation"

The error happens during Cypress tests cleanup when dispatching resetApiState(). The API is use retry() over fetchBaseQuery() with a timeout setting which, browsing the code, uses an AbortController in the fetchBaseQuery().

Checking release notes is likely got introduced in v2.9.2 although glancing at code changes I don't see the immediate culprit but my assumption is that now retry() propagates the abort signal to fetchBaseQuery() and trigger the error.

My stacktraces are bundled as I run e2e tests on the vite build so I've nothing to paste here that is readable.

[run]   TypeError: Illegal invocation
[run]       at Promise.S [as abort] (http://localhost:3000/assets/rtk-DynrW8Eq.js:1:26029)
[run]       at P (http://localhost:3000/assets/rtk-DynrW8Eq.js:1:57456)
[run]       at g (http://localhost:3000/assets/rtk-DynrW8Eq.js:1:57760)
[run]       at <unknown> (http://localhost:3000/assets/rtk-DynrW8Eq.js:1:64914)
[run]       at <unknown> (http://localhost:3000/assets/rtk-DynrW8Eq.js:1:64830)
[run]       at Object.dispatch (http://localhost:3000/assets/rtk-DynrW8Eq.js:1:20601)
[run]       at Object.resetCache (http://localhost:3000/assets/initGlobals-CbEWBp_i.js:35:148820)
[run]       at Context.eval (webpack://ark.starters.spa/./cypress/support/e2e.ts:11:27)
[run]       at getRet (http://localhost:3000/__cypress/runner/cypress_runner.js:122456:20)
[run]       at tryCatcher (http://localhost:3000/__cypress/runner/cypress_runner.js:1777:23)

getResetApiActions = () => [
  myApi1.util.resetApiState(),
  myApi2.util.resetApiState(),
];

resetCache = () => {
  for (const x of getResetApiActions())
    store.dispatch(x);
}

[markerikson]

Yeah, we started passing through the abort behavior in #5114 .

Can you provide a repro for this issue? This doesn't give me enough info to investigate.

[AndreaCuneo]

@markerikson I don't have a "small reproduction" atm but is reproducible at this specific commit running tests.

My expectation would be that that adding the { timeout } param to fetchBaseQuery in this test would have fetchBaseQuery create the AbortController() which cause the issue.

[AndreaCuneo]

@markerikson ok, this is tricky indeed. I tried to reproduce within a fork of this, with no success but the test infrastructure may interfere or I wasn't able to actually reproduce.

Thus I created a standalone TS and I was able to reproduce a different error "TypeError: Cannot read private member #signal from an object whose class did not declare it" which at least was linked to 'Abort'.

Thus I suspected (well, with Copilot help I have to admit) that the Node runtime was somewhat different than the Cypress=Browser one. Converting the TS to MJS and using a CDN, here we have a reproducible HTML example (check console).

https://gist.github.com/AndreaCuneo/9d47c5ef78b0777e3549e10d9edec2f1

Downgrading version of CDN or commenting the {timeout} extraOption on endpoint removes the Error.

Browser stacktrace points here but I don't get it as I don't see how that abort() loses the 'this' of the abortController.

I suspect that actual issue is here which may be even worse due to signal losing it's this including the eventListener callback losing the abortController.

Unfortunatly I wasn't able to reproduce it under UnitTest otherwise I'd have prepared a PR but without ability to reproduce it from the codebase I cannot confirm my suspects.

[EskiMojo14]

@AndreaCuneo I've opened a PR #5150, can you try installing the build from CodeSandbox there and seeing if it fixes the issue?

[AndreaCuneo]

@AndreaCuneo I've opened a PR #5150, can you try installing the build from CodeSandbox there and seeing if it fixes the issue?

Thanks a lot for the prompt fix.
Today I'm travelling, not sure I can find the time. Will check tomorrow.

[AndreaCuneo]

@markerikson confirmed fixed. Thanks a lot!

Tested both with the reproduction script and by upgrading the codesandbox package in local dev.