Add option to use system scheme instead of scheme returned by useColorScheme in useHideAnimation about react-native-bootsplash

[zoontek]

@kevinranks Just published 5.5.0-rc.1 that use system dark mode setting instead of the Appearance module. Try it! 🙂

[zoontek]

Hi @kevinranks! First, thanks for buying a license, it helps a lot 🙏

Like I said in #484, it's not possible to use the user preferred theme (at least the one enforced in the app) as the system starts showing the splash screen (using android:windowSplashScreenBackground, android:windowSplashScreenBrandingImage, etc), then your app starts. This allow instant opening response, but makes advanced customization impossible.

But there's also something I miss: I tend to never use per-app system settings overrides and I didn't know that the Appearance module was able to override that (for me, this should be done user-side: Appearance.getColorScheme() should return the system preference, but you could be able to override it and saves it in MMKV, AsyncStorage or else)

Knowing that, I will replace the useColorScheme library usage with an exported constant and always respect the system setting instead. Expect a 5.5.0.rc-1 that contain the fix this week-end.

[kevinranks]

Hi @kevinranks! First, thanks for buying a license, it helps a lot 🙏

Like I said in #484, it's not possible to use the user preferred theme (at least the one enforced in the app) as the system starts showing the splash screen (using android:windowSplashScreenBackground, android:windowSplashScreenBrandingImage, etc), then your app starts. This allow instant opening response, but makes advanced customization impossible.

But there's also something I miss: I tend to never use per-app system settings overrides and I didn't know that the `Appearance` module was able to override that (for me, this should be done user-side: `Appearance.getColorScheme()` should return the system preference, but you could be able to override it and saves it in `MMKV`, `AsyncStorage` or else)

Knowing that, I will replace the useColorScheme library usage with an exported constant and always respect the system setting instead. Expect a 5.5.0.rc-1 that contain the fix this week-end.

Thank you! Yeah, Appearance.setColorScheme() allows you to set a local app preferred scheme that overrides what useColorSCheme and getColorSCheme returns. So if this library grabbed the preferred scheme directly from the system instead, it should never end up with the issue of the splash screen switching between screens. And it would still allow developers to use the local color scheme for their app UI.

Will keep an eye on the releases. Thanks again

[zoontek]

Available in 5.5.0

[fahadJariwala]

Hi @zoontek
First of all Thanks for the Amazing library, I have just switched raect-native-splash screen to react-native-bootsplash.
I am getting stuck on setting the system theme instead of the systemColorScheme.
Could you please give me some examples to set systemTheme instead of systemColorScheme

[zoontek]

@fahadJariwala It uses the system theme, not the one defined / overwritten in your app.

As the splash screen starts BEFORE your app (for faster launch), you can't enforce light / dark mode. It follows the system setting.