Changing CSS variables dynamically causes error

[jonathanhuang13]

Current behavior

I have a CSS selector that changes the CSS variable like so:

@layer base {
  :root {
    --primary: theme('colors.red.500');
  }

  .dark:root {
    --primary: theme('colors.blue.500');
  }
}

When I apply that className like so:

export default function HomeScreen() {
  const [dark, setDark] = useState(false);

  return (
    <View className={dark ? 'dark pt-20' : 'pt-20'}>
      <Text className="bg-primary">Hi</Text>
      <Button title="Toggle dark" onPress={() => setDark(!dark)} />
    </View>
  );
}

I get an error:

Error: Couldn't find a navigation context. Have you wrapped your app with 'NavigationContainer'? See https://reactnavigation.org/docs/getting-started for setup instructions.

This only happens if the CSS variables replace an existing CSS variable. For example, this will work:

@layer base {
  :root {
    --primary: theme('colors.red.500');
  }

  .dark:root {
    --primary2: theme('colors.blue.500'); // 'primary2' does not replace 'primary'
  }
}

Expected behavior

Changing the CSS variable should not break React Navigation

Reproduction

https://github.com/jonathanhuang13/expo-css-variables-issue

Platform

• [ ] Android
• [X] iOS
• [ ] Web
• [ ] Windows
• [ ] MacOS

Packages

• [ ] @react-navigation/bottom-tabs
• [ ] @react-navigation/drawer
• [ ] @react-navigation/material-top-tabs
• [ ] @react-navigation/stack
• [ ] @react-navigation/native-stack
• [ ] react-native-tab-view

Environment

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

package	version
@react-navigation/native	6.1.18
react-native	0.74.5
expo	51.0.28
node	20.9
npm	10.1

[github-actions[bot]]

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

• @react-navigation/native (found: 6.0.2, latest: 6.1.18)

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

[jonathanhuang13]

Yes, the issue still exists on 6.1.18

[github-actions[bot]]

Hey @jonathanhuang13! Thanks for opening the issue. It seems that the issue doesn't contain a link to a repro.

The best way to get attention to your issue is to provide an easy way for a developer to reproduce the issue.

You can provide a repro using any of the following:

• Expo Snack
• TypeScript Playground

• GitHub repo under your username

  A snack link is preferred since it's the easiest way to both create and share a repro. If it's not possible to create a repro using a snack, link to a GitHub repo under your username is a good alternative. Don't link to a branch or specific file etc. as it won't be detected.

  Try to keep the repro as small as possible by narrowing down the minimal amount of code needed to reproduce the issue. Don't link to your entire project or a project containing code unrelated to the issue. See "How to create a Minimal, Reproducible Example" for more information.

  You can edit your original issue to include a link to the repro, or leave it as a comment. The issue will be closed automatically after a while if you don't provide a repro.

[satya164]

You need to provide a minimal repro that uses React Navigation directly without any framework.

[github-actions[bot]]

Hello 👋, this issue has been open for more than a month without a repro or any activity. If the issue is still present in the latest version, please provide a repro or leave a comment within 7 days to keep it open, otherwise it will be closed automatically. If you found a solution or workaround for the issue, please comment here for others to find. If this issue is critical for you, please consider sending a pull request to fix it.