fix(modal): restore React mount state reset in unmount() after #2632

[huextrat]

Summary

Fixes a regression introduced in v5.2.11 with #2632 (modal status refactor): after dismissing a BottomSheetModal, React state could keep mount: true, so a later present() (e.g. from useFocusEffect when navigating) would hit the fast path and call snapToIndex(index)—closed sheets appeared to reopen.

Root cause

In v5.2.10, unmount() saved whether the portal was mounted before resetVariables():

const _mounted = mounted.current; // mirrored `mount` each render
resetVariables();
// ...
if (_mounted) {
  setState(INITIAL_STATE);
}

In v5.2.11, the equivalent branch checked statusRef after resetVariables(), which always sets statusRef to INITIAL. The guard therefore never matched and setState(INITIAL_STATE) was skipped.

The condition also only considered PRESENTED and ANIMATING, while a completed dismiss ends as DISMISSED—so it would be wrong even if evaluated before reset.

Fix

Mirror mount into mountRef on every render (same pattern as mounted.current = mount in v5.2.10). In unmount(), read hadReactMount = mountRef.current before resetVariables(), then call setState(INITIAL_STATE) when hadReactMount is true.

Testing

• yarn lint (biome) on ./src passes.
• yarn typescript still reports existing errors in other files on this branch (unchanged by this PR).

Checklist

• Minimal, targeted change
• Maintainer may want a repro example or regression test for modal + navigation

Made with Cursor

[dorupopacaliman]

I can confirm 5.2.11 made my entire app unusable, this needs to be fixed asap

[gorhom]

thanks @huextrat for submitting this PR, tested it and going to publish a new release shortly