[Bug]: Active fetcher is not revalidated when explicit fetcher key is used

[gforro]

What version of React Router are you using?

6.26.2

Steps to Reproduce

I have already reported the bug in remix-run/remix repo, which rather belongs to this repository: https://github.com/remix-run/remix/issues/10053 I have reported it in the remix repository as I have observed the problem in the Remix framework.

Expected Behavior

Active fetcher is revalidated after form submission or when the revalidator.revalidate() is called.

Actual Behavior

Fetcher in a mounted component is not revalidated after form submission or when the revalidator.revalidate is called. This happens only if future.v7_fetcherPersist = false mode is used. The problem can appear only if there are multiple fetchers with the same fetcher key rendered in the very same page (see linked remix-run/remix bug for further detail)