fix: add typeof guard for getBoundingClientRect in useBoundingClientRect

[magrinj]

PR #2561 fixed the unstable_getBoundingClientRect path (line 58) by adding a typeof === 'function' guard, but the fallback getBoundingClientRect path (line 71) was missed, it still only checks !== null.

In react-test-renderer, nativeFabricUIManager is set to {} by React Native's jest setup (react-native/jest/setup.js line 36), which makes isFabricInstalled() return true. This causes the useBoundingClientRect hook to execute the Fabric code path. Since getBoundingClientRect is undefined (not null) on test renderer refs, the !== null check passes and the call crashes:

TypeError: ref.current.getBoundingClientRect is not a function at useBoundingClientRect.ts:73:34

This affects any jest test that renders a BottomSheet component deeply enough to trigger the hook.

Fixes #2625
Reproduction: https://github.com/magrinj/bottom-sheet-test-bug

[SellersEvan]

I am experiencing this issue as well. I believe it started happening on Expo SDK 55.

[chukwumaokere]

@SellersEvan what version are you on? It seems fixed in v5.2.8

[SellersEvan]

@chukwumaokere Just updated and the issues seems to be resolved. Thanks! That's the first thing I should of check.

[kevinmcalear]

I'm having this exact same issue and had to patch using this type of fix

[github-actions]

This PR is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 10 days.

[magrinj]

Seems to still occur regarding the comments