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 issue (#16) started with a positioning problem, which is now fixed, but it revealed another kinda hard to fix problem - displaying the lockscreen when an alertView / actionSheet is visible, or displaying one after the lockscreen is visible results in a few cases:
the lockscreen and the keyboard appear on top the av/as, but
the dimming of the av/as appears on top the lockscreen;
if the app is closed and reopened, the order becomes av/as - lockscreen - dimming - keyboard.
the lockscreen always appears behind the av/as, while the keyboard
doesn't appear until the av/as is dismissed;
appears on top on the av/as - if the app is closed and reopened with the av/as visible.
the lockscreen appears above the av/as, while the keyboard appears below, so there's no way to enter the passcode.
The current implementation shows the lockscreen behind the av/as.
The issue (#16) started with a positioning problem, which is now fixed, but it revealed another kinda hard to fix problem - displaying the lockscreen when an
alertView
/actionSheet
is visible, or displaying one after the lockscreen is visible results in a few cases:The current implementation shows the lockscreen behind the av/as.
Related StackOverflow question: https://stackoverflow.com/questions/19816142/uialertviews-uiactionsheets-and-keywindow-problems. I tried creating a new window, but either it doesn't work, or I simply didn't manage to do it properly.
Any help would be greatly appreciated.
The text was updated successfully, but these errors were encountered: