iOS 9 vs iOS 8.4.1 unresponsiveness due to input-blocking

[trifid]

Hey guys, I found new input-blocking in iOS9 that wasn't present in iOS8.4.1. In the Clock app, a common chore for me is editing alarms, when you click on "Edit" and immediately try to tap an alarm, iOS9 will block input during animation:

I just realized this input blocking extends to any app with similar editing functionality. I just tested 'Edit' in Mail and it has the same input-blocking in iOS9, but not in 8.4.1.

 

[perfect_]

There is a another input block.

- Go to Settings/Wallpaper/Choose: Select Dynamic or Stills (it doesnt matter)
- Touch Choose(Back button)
- immediately touch Dynamic or Stills
(Nothing happens)

iOS 9.3 beta4

 

[iOSUser7]

And another one, this one is pretty bad actually, it's longer than any other else I think :

-Call Siri (you can cancel the voice recognition if you want, we don't need it).
-Pull up control center and immediatly try to pull it down. Depending on how hard you pulled it, it can take a good 3 seconds to pull it down again.

It's really bad and really easy to do.
I'm on 9.2.1 by the way, I don't know if the latest 9.3 beta fixed it. If you are not able to reproduce the bug, I can record a video.

 

[perfect_]

And another one, this one is pretty bad actually, it's longer than any other else I think :

-Call Siri (you can cancel the voice recognition if you want, we don't need it).
-Pull up control center and immediatly try to pull it down. Depending on how hard you pulled it, it can take a good 3 seconds to pull it down again.

It's really bad and really easy to do.
I'm on 9.2.1 by the way, I don't know if the latest 9.3 beta fixed it. If you are not able to reproduce the bug, I can record a video.

Still happening on iOS 9.3 beta4
No improvements.

 

[iOSUser7]

Still happening on iOS 9.3 beta4
No improvements.

Alright, thanks for the report. I can't believe Apple has left so much imput blocking like this while it was perfect in previous iOS versions.

 

[d5aqoëp]

So I was going to update my iPad Air 1 from 8.4.1 to 9.2.1, but I think you guys answered all my questions

I think Air 1 on 8.4.1 is a torrid mess. Safari is practically unstable and unusable. It displays ancient tabs for a split second and crashes randomly. I would suggest that you upgrade to 9.3 as soon as it officially releases.
9.3 should be better than 8.4.1 in terms of stability and safari usefullness. People have even mentioned about reduced UI stutter.

But there will be slightly more input blocking

 

[Silly John Fatty]

I think Air 1 on 8.4.1 is a torrid mess. Safari is practically unstable and unusable. It displays ancient tabs for a split second and crashes randomly. I would suggest that you upgrade to 9.3 as soon as it officially releases.
9.3 should be better than 8.4.1 in terms of stability and safari usefullness. People have even mentioned about reduced UI stutter.

But there will be slightly more input blocking

Yeah I do occasionally have the old tabs appearing, but I don't mind it as long as everything is fast and not too buggy. (the tab issue is not a dramatic thing because it doesn't affect your use)

When 9.3 is released I'll wait to see what people report, but I'm not sure if it will be faster honestly. Well, hopefully it will be released soon.

 

[perfect_]

Another one;
- Open Safari and touch tab button,
- Tap Home button,
- Open Safari and immediately touch active tab or Done button
(Nothing happens)

Screen doesn't respond until the animation is over.

iOS 9.3 beta4

 

[d5aqoëp]

@trifid OP
You need to change the thread's title to "iOS 9 unresponsiveness due to input blocking" to be specific.

 

[trifid]

@trifid OP
You need to change the thread's title to "iOS 9 unresponsiveness due to input blocking" to be specific.

Thanks, that would be better I guess, unfortunately I don't think it's possible to change topic title once started. The title is still appropriate though, since OS is literally unresponsive to the cases I described. I'm adding more videos to OP to show the issue in more detail and to make it more clear too.

 

[C DM]

Thanks, that would be better I guess, unfortunately I don't think it's possible to change topic title once started. The title is still appropriate though, since OS is literally unresponsive to the cases I described. I'm adding more videos to OP to show the issue in more detail and to make it more clear too.

Seems like you should be able to do it using the little gear icon at the top right above the first/OP post in the thread.

 

[trifid]

Seems like you should be able to do it using the little gear icon at the top right above the first/OP post in the thread.

Thanks, didn't know about that, I just changed the title.

 

[Bladery]

What about the new beta 5?
Does it solve any problem?

 

[Act3]

What about the new beta 5?
Does it solve any problem?

iOS 9.3 B5 input blocking is the same, no worse and no better than before in my opinion.

 

[vista980622]

I don't think it will be resolved in the foreseeable future.

 

[C DM]

Apple intends this to happen (for whatever reason it's worth).
View attachment 619669
I don't think it will be resolved in the foreseeable future.

Seems like pretty much the conclusion many of us have come to and/or accepted since iOS 7 days.

 

[trifid]

Apple intends this to happen (for whatever reason it's worth).
View attachment 619669
I don't think it will be resolved in the foreseeable future.

“If you have questions about the resolution, or if this is still a critical issue for you, then please update your bug report with that information”

Seems like Apple is still open to further discussion about it.

For what it's worth I don't consider this issue resolved, and will continue documenting anything I find.

If one looks at the Clock UI video I uploaded for example, it's just laughable that iOS would do this. Look at that video, there is no way on Earth that's good design.

If anyone feels the same, I just hope people keep reporting it, it can't hurt.

 

[Act3]

Seems like pretty much the conclusion many of us have come to and/or accepted since iOS 7 days.

Maybe but the video in the OP shows its a lot worse in 9.1 compared to 8.4.1

It was resolved with some version of iOS 7 and has made it back with iOS 9

 

[C DM]

Maybe but the video in the OP shows its a lot worse in 9.1 compared to 8.4.1

It was resolved with some version of iOS 7 and has made it back with iOS 9

The degrees to which it was and is around might have fluctuated between some versions, but it has been noticeably off from pre-iOS 7 days petty much no matter what post-iOS 7 version is in question.

 

[Act3]

The degrees to which it was and is around might have fluctuated between some versions, but it has been noticeably off from pre-iOS 7 days petty much no matter what post-iOS 7 version is in question.

IMO, any version of 9 is/has been less responsiveness than any other version of iOS that I have used. I've owned every version of iPhone since the 3GS minus the plus sizes.

 

[Bladery]

Apple must kidding us! This is a joke that they say this behavior is intended!
They urgently need to fix that!

 

[vista980622]

“If you have questions about the resolution, or if this is still a critical issue for you, then please update your bug report with that information”

Seems like Apple is still open to further discussion about it.

For what it's worth I don't consider this issue resolved, and will continue documenting anything I find.

If one looks at the Clock UI video I uploaded for example, it's just laughable that iOS would do this. Look at that video, there is no way on Earth that's good design.

If anyone feels the same, I just hope people keep reporting it, it can't hurt.

I have added the specific examples mentioned in the top thread, every video I can find relating to the issue, URL of this thread to the bug report. I have also extensively discussed its implications, where at often times, an animation is already visually finished to users (almost finished, easing out, etc.), yet their taps still fail to register. This will cause the user to tap several times, which is unnecessary and burdensome.

I wish they can reverse their course. Also worth trying is to get medias report upon this issue. See how the blocking of Apple pencil navigation was addressed hours after media attention.

If anyone wants to dupe my radar, dupe rdar://24874703
[doublepost=1457153925][/doublepost]Also worth mentioning, there is a bug in iOS 9 that you can manually trigger, where the bug can completely disable all animations in SpringBoard. No cross fades. No ease in/outs. Any input is instantly recognized and reacted upon.

Personally, this makes the input-blocking issue acceptable for me, since when animations are off, there is nothing left to block my inputs.

That's my favorite bug and I wish it never get fixed.

 

[trifid]

I have added the specific examples mentioned in the top thread, every video I can find relating to the issue, URL of this thread to the bug report. I have also extensively discussed its implications, where at often times, an animation is already visually finished to users (almost finished, easing out, etc.), yet their taps still fail to register. This will cause the user to tap several times, which is unnecessary and burdensome.

I wish they can reverse their course. Also worth trying is to get medias report upon this issue. See how the blocking of Apple pencil navigation was addressed hours after media attention.

If anyone wants to dupe my radar, dupe rdar://24874703
[doublepost=1457153925][/doublepost]Also worth mentioning, there is a bug in iOS 9 that you can manually trigger, where the bug can completely disable all animations in SpringBoard. No cross fades. No ease in/outs. Any input is instantly recognized and reacted upon.

Personally, this makes the input-blocking issue acceptable for me, since when animations are off, there is nothing left to block my inputs.

That's my favorite bug and I wish it never get fixed.

You are awesome dude, great bug report. I'm also looking into that animation bug thing, that might be a great temporary fix until Apple decides to get their act together.

One last thing, you are right on the media thing, I will try to keep documenting this through more videos covering more use cases. Hopefully this will get more exposure and someone might pick this up.

 

[imagineadam]

I have added the specific examples mentioned in the top thread, every video I can find relating to the issue, URL of this thread to the bug report. I have also extensively discussed its implications, where at often times, an animation is already visually finished to users (almost finished, easing out, etc.), yet their taps still fail to register. This will cause the user to tap several times, which is unnecessary and burdensome.

I wish they can reverse their course. Also worth trying is to get medias report upon this issue. See how the blocking of Apple pencil navigation was addressed hours after media attention.

If anyone wants to dupe my radar, dupe rdar://24874703
[doublepost=1457153925][/doublepost]Also worth mentioning, there is a bug in iOS 9 that you can manually trigger, where the bug can completely disable all animations in SpringBoard. No cross fades. No ease in/outs. Any input is instantly recognized and reacted upon.

Personally, this makes the input-blocking issue acceptable for me, since when animations are off, there is nothing left to block my inputs.

That's my favorite bug and I wish it never get fixed.

How do I activate this bug that disables animations??!

 

[perfect_]

I am sad.