Guy Carmeli

@shay127 Perhaps submit a PR so it's easier for the maintainers to accept the suggested change.

@phepsi Can you push your reproduction so I can debug the issue?

We've been using the [following approach](https://github.com/wix/react-native-navigation/blob/b53f13c60fe6498ad1690adf1dfd7509f602965c/lib/src/adapters/NativeEventsReceiver.ts#L23) to work around this issue In [wix/react-native-navigation](https://github.com/wix/react-native-navigation). Been using it for 4 years without any issues, we can submit a PR if you're interested.

gotcha! This issue reproduces for us in "3.2.x". We'll try v4 once it's out of beta and report back.

We'll submit a PR next week 👍

@NagRock This library has been a life-saver for us. A lot of people would appreciate it if you gave access to someone so the project can continue. You've done amazing...

Hey @sorodrigo 👋 We've stopped maintaining v1, so the sort answer is no. Meanwhile, If you're interested, you can migrate to v2 easily using this [library](https://github.com/wix-playground/react-native-navigation-v1-v2-adapter).

@pribeh This issue will be prioritized in the coming weeks. We're going to draw a roadmap for the upcoming quarter soon and this issue will be definitely be high priority.

I think passing `null` is preferred to disabling StatusBar color all together for Overlays. That might require small changes to `OptionsProcessor.processColor`, not sure how it currently handles null.

If you access RNN's publish api (push, pop etc) through a dedicated service (or swizzle Navigation.showOverlay), you can enforce any style properties you want.