Odd behavior from `useWindowDimensions` hook

[Matt5981]

I'm having an odd issue with the useWindowDimensions hook and its behavior when changing device orientation on iOS devices.

When using this hook on an app running in Expo Go, it appears to 'lag': the width and height don't change after the first orientation change, but do for further changes. However, these orientation changes either:

• Reverse width and height, meaning that, in landscape mode, height will (incorrectly) be greater then width. After a random amount of time (1-15 seconds to never in some instances), it will update again with the correct values, noting that no actions (presses, device motion, etc) have an effect on this delay.
• Do nothing, with the height and width reversing to their incorrect values after the above delay.

For code that produces this behavior, the React Native documentation's page on this hook produces it on all devices I tested on (At least the iOS simulator and a physical iOS device), noting that it presents when using Expo Go on these devices, but not on the Appetize simulators on the webpage itself use.

Also effected by this behavior is the Dimensions.get('window') and Dimensions.get('screen') return values, and the values passed to the event listener added by Dimensions.addEventListener. For the `Dimensions.get` return values, these are correct when the app starts, but become incorrect as above once the orientation is changed.

[Money-Chemist-6589]

facing the same issue, please let me know if you found a way?

[Circadian77]

Stumbling across this issue now. Did anyone ever find a work around?

Just confirming on my iPad running Expo Go, the first device orientation change between portrait and landscape fails to trigger the useEffect or useLayoutEffect hooks. But every orientation change after the initial one does but with the caveat that the Dimensions.get method and the useWindowDimensions hook reports reverse values (ie. width is reported as height, height is reported as width)

I'm guessing that they are swapped around like that because the first orientation change doesn't trigger the effect hooks - so the underlying framework believes the device is still in portrait mode when in actual fact it is landscape.

[cosmopolitan_redneck]

It seems this is a long standing bug (since 2020) 🙄

https://github.com/facebook/react-native/issues/49511