useColorScheme is not working with fullScreenModal

[saintyusuf]

Current behavior

When I'm using useColorScheme from react-native, fullScreenModal's background is not changing dynamicly when I turn on/off dark mode on iPhone.

Expected behavior

It must work but it's not. But I already solved it!

I changed the fullScreenModal to containedModal and all dynamic styles are working now.

Reproduction

it's not needed in this case

Platform

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

Packages

• [X] @react-navigation/bottom-tabs
• [ ] @react-navigation/drawer
• [ ] @react-navigation/material-top-tabs
• [X] @react-navigation/stack
• [X] @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.9"
@react-navigation/bottom-tabs	"^6.5.11"
@react-navigation/drawer
@react-navigation/material-top-tabs
@react-navigation/stack
@react-navigation/native-stack	"^6.9.17"
react-native-safe-area-context	"4.6.3"
react-native-screens	"~3.22.0"
react-native-gesture-handler
react-native-reanimated	"~3.3.0"
react-native-tab-view
react-native-pager-view
react-native	"0.72.10"
expo	"~49.0.15"
node	v20.10.0
npm or yarn	npm: 10.2.3

[github-actions[bot]]

Couldn't find version numbers for the following packages in the issue:

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

Can you update the issue to include version numbers for those packages? The version numbers must match the format 1.2.3.

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

• @react-navigation/native (found: 6.1.9, latest: 6.1.17)
• @react-navigation/bottom-tabs (found: 6.5.11, latest: 6.5.20)

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

[github-actions[bot]]

Hey @saintyusuf! 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.