-
Notifications
You must be signed in to change notification settings - Fork 24.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Apperance.getColorScheme() returns incorrect value if app opened in background (e.g. using Healthkit.HKObserverQuery) #46015
Labels
Resolution: Fixed
A PR that fixes this issue has been merged.
Comments
react-native-bot
added
Needs: Author Feedback
Needs: Repro
This issue could be improved with a clear list of steps to reproduce the issue.
labels
Aug 14, 2024
|
|
|
|
I have the same issue but with |
@RodolfoGS Yeah, you can try that fix. |
Thanks all, yep will try that and use as a patch. |
github-actions
bot
added
Needs: Attention
Issues where the author has responded to feedback.
and removed
Needs: Author Feedback
labels
Aug 15, 2024
cortinico
added
Resolution: Fixed
A PR that fixes this issue has been merged.
and removed
Needs: Repro
This issue could be improved with a clear list of steps to reproduce the issue.
Needs: Attention
Issues where the author has responded to feedback.
labels
Aug 21, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Description
When using a background process like Healthkit.HKObserverQuery it will wake up the app in the background to process new activities in HealthKit. When this happens Apperance.getColorScheme() will return 'light' even if the system color scheme is 'dark'
Steps to reproduce
React Native Version
0.74.3
Affected Platforms
Runtime - iOS
Output of
npx react-native info
Stacktrace or Logs
Reproducer
I created a new native module in iOS to test if it was a iOS or RN bug. The below code will return the correct value so hence its a bug with RN
Screenshots and Videos
No response
The text was updated successfully, but these errors were encountered: