Skip to content


Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP


Calling a 2nd Alert/Sheet in a Block causes Window issues #28

coneybeare opened this Issue · 10 comments

8 participants


There are several valid reasons why a seconds alert view would be called after a sheet button was tapped, or text entry was entered. In my app, I use it to throw validation errors, etc....

Before the code for the first alert/sheet is run to make it animate out, the second alert show code gets triggered from the block and gets added to the view. The problem is that after the first alert subsequently animates out, it returns key focus to what it assumes is the previous top window. But at this point, the window of the second alert is on top of the previous top window.

This means that the second alert/sheet will be on screen and forefront, but will be unresponsive as all the taps are sent to the previous top window.

There are a few ways to tackle this... One way is simply telling people not to do this. I think a better way though is to emulate the default UIAlertView and AlertSheet behavior. When 2 UIAlertViews are set to call, they are queued in some internal mechanism, and the second is shown after the first is dismissed. This would solve the problem and make it more robust in the future as it ensures that only 1 alert or sheet is on screen at any given time, and prevents the bug described above. Thoughts?


I faced the same issue and put in a few small and very simple changes (not sure if this clean enough, but seems to be ok thus far, at least in my testing.

Now you can push multiple BlockAlerts into a queue and they are shown in sequence once one is dismissed. Let me know if this is the right direction to go with this.


I think this is the wrong approach. I implemented it in BlockBackground so the queue would also prevent BlockActionSheets from showing over BlockAlertViews. Unfortunately, my code has strayed quite far from your original so a pull request is probably out of the question, but I can send you a link over DM if you would like to take a look my approach.


Ahh, since I didn't use BlockActionSheets in my project, I overlooked them.


I am also have same issue as explained above. I have a game app which is question answer app so there are lot of pop ups coming and going and if the user taps some pop up fast enough, the BlockAlertView goes to unresponsive state as @coneybeare explained in 1st post. Did you guys come up with any solutions? Any advice suggestions are highly appreciated.

Thank you!


I solved it in my app called The Last Shot, but the changes are too drastic to merge a pull request here. I used the same approach as I described 3 comments up.


I'd love to see a fix for this using a queue.

For now I patched it by modifying the dismissWith... function to keep track of the last time an alert was dismissed. Then changed the show function to delay itself if necessary - to give the animating alert enough time to dismiss. Huge hack, but took 15 lines & lets me stack alerts.


I fixed by adding the following statements in BlockAlertView.m and BlockActionSheet.m.
It seem to works better.


- (void)show
    if ([BlockBackground sharedInstance].keyWindow) {
        [self performSelector:@selector(show) withObject:nil afterDelay:0.3];

and in BlockActionSheet.m

- (void)showInView:(UIView *)view
    if ([BlockBackground sharedInstance].keyWindow) {
        [self performSelector:@selector(showInView:) withObject:view afterDelay:0.3];

but i don't use BlockTextPromptAlertView, so i don't have solution for this.



Just a note that the above didn't work for me. I instead altered it so that instead of:

if ([BlockBackground sharedInstance].keyWindow)

it used:

if (![BlockBackground sharedInstance].hidden)

Seems to be working at the moment.


I experienced the same problem, could you maybe upload the code fix to the repo ?


This should be fixed by 09d3b71

@barrettj barrettj closed this
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Something went wrong with that request. Please try again.