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
Describe the bug
When UIApplication.shared.statusBar.style is default and SwiftEntryKit is displayed and closed, the style is rewritten to either .lightContent or .darkContent.
So I thought It needed to add a new case.default to EkAttributes.StatusBar.
To Reproduce
Steps to reproduce the behavior:
Set UIApplication.shared.statusBar.style to .default.
Set the device to dark mode.
show SwiftEntryKit
close Swift
status bar style is overridden to .darkContent
Expected behavior
A clear and concise description of what you expected to happen.
Screenshots
If applicable, add screenshots to help explain your problem.
iPhone (please complete the following information):
iPhone 11 Pro
iOS 15.5
Xcode Version 13.3.1
Dependency Manager Version SPM
SwiftEntryKit Release # [e.g. 0.2.0]
Additional context
Add any other context about the problem here.
Screenshots / Video Links
The text was updated successfully, but these errors were encountered:
p-x9
changed the title
StatusBar appearance is overwritten by SwiftEntryKit after the alert is dismissed.
StatusBar Style is overwritten by SwiftEntryKit after the alert is dismissed.
May 23, 2022
Describe the bug
When UIApplication.shared.statusBar.style is
default
and SwiftEntryKit is displayed and closed, the style is rewritten to either.lightContent
or.darkContent
.related to this codes
SwiftEntryKit/Source/Model/EntryAttributes/EKAttributes+StatusBar.swift
Lines 58 to 68 in cf1cde7
So I thought It needed to add a new case
.default
to EkAttributes.StatusBar.To Reproduce
Steps to reproduce the behavior:
.default
..darkContent
Expected behavior
A clear and concise description of what you expected to happen.
Screenshots
If applicable, add screenshots to help explain your problem.
iPhone (please complete the following information):
Additional context
Add any other context about the problem here.
Screenshots / Video Links
The text was updated successfully, but these errors were encountered: