One throws `React state update on a component that hasn't mounted yet` when using Tab navigator with more then one tab

[christianjuth]

When I create a new One project using One 1.1.392 I am getting a React error when using the tab navigator.

1. Clone the reproduction repo
2. npm i
   • You may need to add the --force flag as the default one template with npm has been giving me issues recently
3. npm run dev
4. Open in Expo Go
5. You should see the following error

[error] Can't perform a React state update on a component that hasn't mounted yet. This indicates that you have a side-effect in your render function that asynchronously later calls tries to update the component. Move this work to useEffect instead. {"name":"Component Stack"}

Interestingly, if I only register one <Tab.Screen /> I don't get the error, but as soon as I add the second I see the error.

[justinmclaren]

Try updating to the latest version of 'one'. That fixed this exact issue for me.

[christianjuth]

@justinmclaren I still see the error. Also glanced at the commits and I don't think I saw any change to the tab navigation, though I might be wrong about that part.

[natew]

This appears to be a React Navigation initialization issue specific to tab navigators with multiple screens on React Native.

The error "Can't perform a React state update on a component that hasn't mounted yet" typically happens when:

1. Navigation state is being updated before the navigator component has fully mounted
2. Async operations try to update state during the initial render phase

A few things to try:

1. Wrap your tab navigator in a conditional render:

const [isReady, setIsReady] = useState(false)
useEffect(() => setIsReady(true), [])
if (!isReady) return null
return <Tabs>...</Tabs>

2. Check if you have any navigation effects running on mount in your tab screens

3. Try using lazy={true} on Tab.Screen to delay screen initialization

Could you also share:

• Your One version (latest?)
• Your _layout.tsx file with the Tabs setup
• Whether this happens with a minimal tab setup (just empty screens)

This will help isolate whether it's a One framework issue or a React Navigation configuration issue.