Screen freeze after update FlatList data and go back

Description

Screen freeze after updating FlatList data and return to the previous screen

App does not freeze when:

1. Used ScrollView instead FlastList or
2. Downgrade react-native-screens to 2.18.0 or
3. Add detachInactiveScreens={false} for Stack Navigator

Screenshots

https://user-images.githubusercontent.com/14233750/152067342-08ee546b-dd1c-462f-9c28-d0ebebc0d954.mp4

Steps To Reproduce

1. Create 2 Stack Screens
2. Go to Second Screen which display FlastList
3. Add new item to FlatList
4. Go back to First Screen

Expected behavior

First Screen not freeze

Actual behavior

First screen freeze, and cannot click on button

Reproduction

const First = ({ navigation }) => {
  return (
    <View>
      <Button title="click" onPress={() => navigation.navigate('Second')} />
    </View>
  );
};
const Second = ({ navigation }) => {
  const [numbers, setNumbers] = useState([1, 2, 3]);
  return (
    <View>
      <FlatList data={numbers} renderItem={({ item }) => <Text>{item}</Text>} />
      <Button title="add" onPress={() => setNumbers((a) => [...a, 1])} />
      <Button title="back" onPress={() => navigation.goBack()} />
    </View>
  );
};

const RootNavigation: React.FC = () => {
  const RootStack = createStackNavigator();

  return (
    <NavigationContainer>
      <RootStack.Navigator>
        <RootStack.Screen name="First" component={First} />
        <RootStack.Screen name="Second" component={Second} />
      </RootStack.Navigator>
    </NavigationContainer>
  );
};

export default RootNavigation;

Platform

• iOS
• Android
• Web
• Windows
• tvOS

3.

package	version
react-native	0.66.3
@react-navigation/native	6.0.6
@react-navigation/stack	6.0.11
react-native-screens	3.10.2
react-native-safe-area-context	3.3.2
react-native-gesture-handler	1.10.3
react-native-reanimated	2.3.0-beta.3

[totodot]

Update react-native-reanimated to 2.4.1 resolved the problem

[anhnch]

I confirm tododot’s info 2. Downgrade react-native-screens to 2.18.0 3. Add detachInactiveScreens={false} for Stack Navigator

This is definitely a bug or the 3 points should be written in the official documents. I hope someone can fix it.