ironforward

i ran into this issue as well, and found it was not the child view that was missing but instead it was the ancestor; after setting `collaspable={false}` on the ancestor...

also using EAS and experiencing this behavior. i can call `ScreenOrientation.unlockAsync()` and then `ScreenOrientation.getPlatformOrientationLockAsync()` will return ``` { screenOrientationArrayIOS: [ 1, // Orientation.PORTRAIT_UP 3, // Orientation.LANDSCAPE_LEFT 4, // Orientation.LANDSCAPE_RIGHT ]...

a quick update, setting the expo.ios.infoPlist option in app.json to support landscape like so: ``` "infoPlist": { "UISupportedInterfaceOrientations": [ "UIInterfaceOrientationLandscapeRight", "UIInterfaceOrientationLandscapeLeft", "UIInterfaceOrientationPortrait" ], "UISupportedInterfaceOrientations~ipad": [ "UIInterfaceOrientationLandscapeRight", "UIInterfaceOrientationLandscapeLeft", "UIDeviceOrientationPortrait", "UIDeviceOrientationPortraitUpsideDown" ]...

Surprisingly even though the expo-screen-orientation library fails to detect orientation changes, DeviceMotion does not. So, as a workaround for now if you only need 1 or a few screens to...