Unexpected layout size when screen is out of focus

[oliviercperrier]

Current behavior

Im using a expo-linear-gradient lib and i noticed that when i change screen, the linearGradient is changing orientation. So when i come back the screen with the linearGradient, i see a quick flicker during the time the linearGradient is coming back to normal.

When i load the screen, i get this:

When i change screen:

Issue suspected to come from somewhere here:

react-navigation/packages/react-native-tab-view/src/SceneView.tsx

Lines 74 to 91 in d0abdee

	const focused = navigationState.index === index;
	return (
	<View
	accessibilityElementsHidden={!focused}
	importantForAccessibility={focused ? 'auto' : 'no-hide-descendants'}
	style={[
	styles.route,
	// If we don't have the layout yet, make the focused screen fill the container
	// This avoids delay before we are able to render pages side by side
	layout.width
	? { width: layout.width }
	: focused
	? StyleSheet.absoluteFill
	: null,
	style,
	]}
	>

Expected behavior

Screen layout width and height should stay the same when out of focus to avoid causing weird flicker on resizing when getting back the focus.

Here is an exemple with the linear gradient: https://github.com/expo/expo/assets/28421005/707dc5ea-715c-4a40-a091-0e058f9936b0

Reproduction

https://github.com/oliviercperrier/repro-Expo-linear-gradient-issue

Platform

• Android
• iOS
• Web
• Windows
• MacOS

Environment

• I've removed the packages that I don't use

package	version
expo	^50.0.14
react-native	^0.73.6
@react-navigation/native	~6.1.6
node	v18.19.0
npm	10.2.3

related: expo/expo#28298

[github-actions]

Couldn't find version numbers for the following packages in the issue:

• @react-navigation/native

Can you update the issue to include version numbers for those packages? The version numbers must match the format 1.2.3.

[github-actions]

The versions mentioned in the issue for the following packages differ from the latest versions on npm:

• @react-navigation/native (found: 6.1.6, latest: 6.1.17)

Can you verify that the issue still exists after upgrading to the latest versions of these packages?