Originally created by: BilgeGates
Originally owned by: BilgeGates
What happened?
useHistoryHydration checks isMountedRef.current before calling setState, but the async syncStorage.get() promise is already in flight at unmount time. The state update can still fire because the check races with the in-flight promise resolving after the ref is set to false.
File: src/shared/hooks/fenHistory/useHistoryHydration.ts
Steps to reproduce
- Open the History page
- Navigate away immediately before data finishes loading
- Check the console for setState-after-unmount warnings
Expected
No state updates fire after the component unmounts.
Actual
The isMounted check races with the in-flight promise — state update can still fire after unmount.
Root cause
The isMounted pattern doesn't cancel in-flight promises. An AbortController or a cancellation flag checked inside the promise chain (not after await) is needed.
Browser & OS
Any browser / OS — reproducible in Chrome on desktop with slow network throttling.
Before submitting
- [x] I searched existing issues and this is not a duplicate.
