-
Notifications
You must be signed in to change notification settings - Fork 1k
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
bug: SplashScreen.splashImmersive does not hide status bar #2934
Comments
that is Android only preference, should be documented |
Oh, okay. But why? iOS provides such functionality as I can see and mentioned above. Maybe I turn this into a feature request then? |
Because immersive mode is an android thing, not an iOS thing |
Okay, I understand that. Then how do I enable this functionality for iOS? Manually through |
iOS app are already full screen, the status bar is "transparent", |
You can simply run any starter and try to remove the status bar with |
Does this bug really got fixed? I'm still facing the issue with the latest capacitor on android device.
|
Thanks for the issue! This issue is being locked to prevent comments that are not relevant to the original issue. If this is still an issue with the latest version of Capacitor, please create a new issue and ensure the template is fully filled out. |
Bug Report
Capacitor Version
npx cap doctor
output:Affected Platform(s)
Current Behavior
Enabling
splashImmersive
does not hide the status bar on app start up. I had to manually setUIStatusBarHidden
to true but this causes another error where the status bar appears a millisecond between start up and showing the splash screen with the spinner.Expected Behavior
Enabling this option should hide the status bar until ready state is called.
Sample Code or Sample Application Repo
Reproduction Steps
With any ionic starter:
splashImmersive
to trueionic capacitor run ios --livereload
UIStatusBarHidden
in Plist to trueOther Technical Details
npm --version
output: 6.13.4node --version
output: 12.16.1pod --version
output (iOS issues only): 1.8.3Other Information
The text was updated successfully, but these errors were encountered: