react-native-collapsible-tab-view icon indicating copy to clipboard operation
react-native-collapsible-tab-view copied to clipboard

Error with Tabs.SectionList component

Open enisit opened this issue 3 months ago • 2 comments

Summary

React Compiler is throwing an error [Error: Argument appears to not be a ReactComponent. Keys: ] when using Tabs.SectionList from react-native-collapsible-tab-view library.

Environment

  • Expo SDK: 54.0.0
  • React: 19.1.0
  • React Native: 0.81.4
  • react-native-collapsible-tab-view: 8.0.1
  • React Compiler: Enabled
  • Platform: iOS/Android

Error Details

[Error: Argument appears to not be a ReactComponent. Keys: ]

Current Workaround

We've implemented a temporary workaround by:

  1. Replacing Tabs.SectionList with Tabs.FlatList
  2. Manually flattening the sectioned data structure
  3. Implementing custom header rendering logic

Reproduction Steps

  1. Enable React Compiler in Expo configuration
  2. Use Tabs.SectionList from react-native-collapsible-tab-view
  3. The error occurs during runtime

Expected Behavior

Tabs.SectionList should work seamlessly with React Compiler without throwing component analysis errors.

Actual Behavior

React Compiler fails to analyze the Tabs.SectionList component, throwing an error about invalid React components.

Impact

  • Forces workarounds that reduce code maintainability
  • Limits the use of sectioned lists in collapsible tabs
  • May affect other similar libraries

Additional Context

  • This issue appeared after updating to Expo SDK 54 and enabling reactCompiler
  • The workaround maintains functionality but reduces code clarity

Related Dependencies

{
  "react-native-collapsible-tab-view": "8.0.1",
  "expo": "^54.0.0",
  "react": "19.1.0"
}

enisit avatar Sep 24 '25 12:09 enisit

Indeed, it's unclear to me why this happens. I have seen it while working on #483

If anyone has some time to look into it, please update here. I suspect there's an upstream bug in either reanimated or react-native somewhere.

andreialecu avatar Sep 24 '25 12:09 andreialecu

Indeed, it's unclear to me why this happens. I have seen it while working on #483

If anyone has some time to look into it, please update here. I suspect there's an upstream bug in either reanimated or react-native somewhere.

It seems this is a bug with the new version of react-native-reanimated. I’ve created a minimal reproducible repo, reported it to the team, and the issue link is as follows:

https://github.com/software-mansion/react-native-reanimated/issues/8294

chinamcafee avatar Sep 24 '25 22:09 chinamcafee