[iOS] Build failure: undeclared identifier 'RNSBottomTabsScreenComponentView' on 4.24.0 (Fabric)

[vurhd]

Description

After upgrading to react-native-screens 4.24.0, iOS builds fail with undeclared identifier errors for RNSBottomTabsScreenComponentView and RNSBottomTabsHostComponentView. Android builds succeed. The app does not use native bottom tabs.

Error

- use of undeclared identifier 'RNSBottomTabsScreenComponentView'
- use of undeclared identifier 'RNSBottomTabsHostComponentView'
- unknown type name 'RNSBottomTabsScreenComponentView'; did you mean 'RNSTabsScreenComponentView'?
- unknown type name 'RNSBottomTabsScreenComponentView'; did you mean 'RNSTabsScreenComponentView'?
- unknown type name 'RNSBottomTabsHostComponentView'; did you mean 'RNSTabsHostComponentView'?
- unknown type name 'RNSBottomTabsHostComponentView'; did you mean 'RNSTabsHostComponentView'?

The Xcode build fails during the "Run fastlane" step in the Xcode build process. The errors suggest RNSBottomTabsScreenComponentView and RNSBottomTabsHostComponentView are referenced by the Fabric component provider but their implementations are not being compiled.

Steps to reproduce

1. Use react-native-screens 4.24.0 with New Architecture (Fabric) enabled
2. Build for iOS
3. Xcode fails during compilation with the above errors

Expected behavior

iOS build should succeed as it did on 4.23.0.

Workaround

Pin react-native-screens to 4.23.0.

Environment

• react-native-screens: 4.24.0
• react-native: 0.81.6
• expo: 54.0.33
• @react-navigation/bottom-tabs: 7.14.0
• New Architecture (Fabric): enabled
• Platform: iOS (Android builds fine)

[github-actions]

Hey! 👋

It looks like you've omitted a few important sections from the issue template.

Please complete Snack or a link to a repository, Screens version, React Native version and Platforms sections.

[github-actions]

Hey! 👋

The issue doesn't seem to contain a minimal reproduction.

Could you provide a snack or a link to a GitHub repository under your username that reproduces the problem?

[kmichalikk]

Hi @vurhd,
this is most likely because of expo using our native classes that we refactored, and they're preparing a patch for it here (I looked it up now, it's just been pushed). Anyways, we won't be able to help more here.