You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The first view controller in my UINavigationController has a transparent UINavigationBar (by setting the background image to UIImage()) with a dark image underneath - the status bar is set to lightContent correctly.
The second view controller sets the UINavigationBar background image to nil, and sets the background to light grey (in the viewWillAppear() lifecycle method) but the status bar remains lightContent, when it should display as the default black.
Is this desired behaviour for this module?
The text was updated successfully, but these errors were encountered:
statusBarUpdater?.refreshStatusBarStyle() has to be called whenever the status bar should be refreshed - but this has to be called on the original instance of Bartinter that is watching for changes behind the status bar. In my case this was in the main root view controller called WrapperViewController. Unfortunately it doesn't work to simply call that function on the current VC.
I've set up a shared instance of WrapperViewController, and added the following lifecycle override to the view controllers in my UINavigationController:
Would be nice to put this behaviour into the Bartinter module itself, but it will probably require method swizzling the viewDidAppear method. Not sure how safe that is.
The first view controller in my
UINavigationController
has a transparentUINavigationBar
(by setting the background image toUIImage()
) with a dark image underneath - the status bar is set tolightContent
correctly.The second view controller sets the
UINavigationBar
background image tonil
, and sets the background to light grey (in theviewWillAppear()
lifecycle method) but the status bar remainslightContent
, when it should display as the default black.Is this desired behaviour for this module?
The text was updated successfully, but these errors were encountered: