Mark Erikson

@martynasgz my conclusion looking at the earlier sandbox was that it was expected behavior given the specific app settings they have. If you can provide yours, that would help see...

Hmm. Is this possibly related to the autobatching and `requestAnimationFrame` usage as discussed in #5051 ? What happens if you change the default timer option, like this? ```ts const store...

It might not be `useSyncExternalStore` per se, but rather the `autoBatch` enhancer, which defaults to using `requestAnimationFrame` as the timing mechanism to trigger some updates: - https://redux-toolkit.js.org/api/autoBatchEnhancer What happens if...

Are there any cache-clearing actions dispatched in the Redux store?

In theory, as long as there's active subscriptions, that data should stay in the store, and as long as those components are still mounted there won't have been any unsubscribe...

Can you provide a sandbox or repo that reproduces this issue? Seems extremely odd that there isn't a response here.

@preetish-brine I'm looking at the sandbox example app and I don't see any errors like this. Are there specific steps to reproduce? Does this demo actually show the error, or...

Any chance you could put together an updated version that actually shows this error happening with _some_ consistency? Just based on that retry bit I can't see anything that seems...

Hmm. Actually, I missed reading the section about "if the fetch fails, `meta.response` isn't set". That seems plausible.

Okay, yeah, I can see that if I _force_ the `fetchFn` to return something that _isn't_ a `Response`, the `response.clone()` line fails. However, that whole block of logic is written...