Sidebar Sidebar
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.

When typing a notification reply, it closes if you press the space bar wrong

S

sxc

macrumors member
Original poster
Sep 24, 2007
75
17
If you are replying to a notification in the notification center (eg a whatsapp notification, or facebook messenger notification), when typing, if you press the space bar wrong - in the space just below the space bar - the reply will close and you will lose everything that you typed.

This is VERY frustrating. I guess this is part of the iPhone X swipe up function, and it is interpreting the mis press as a swipe up.

Anyone know how to get around this, aside from typing very slowly and deliberately?
 
  • Like
Reactions: MyMacintosh and macfacts
I have a similar but slightly different issue. When replying to a notification, I get kicked into another app from the notifications list. So if I'm writing a response to an iMessage, I might get kicked into Facebook suddenly because there was a FB notification beneath it on the list. Somehow when you press a certain part of the pop-up keyboard, it registers as a press *below* the keyboard, onto whatever layer is underneath.
 
I wish this would get fixed! It has made replying to notifications from the notification centre impossible!!
 
  • Like
Reactions: eyeseeyou
Still not fixed for whatsapp with iOS 11.1
 
This happens to me as well, thought I was the only one facing this issue on my SE. I filed a bug report for it but Apple obviously ignored it for 11.1, considering they had time to fix it since beta 5 say on everyone’s devices for a week plus.
 
I'm on 10.3.3 and this happens all the time there too. I just have just grown to avoid using quick reply since it doesn't seem to be a priority for Apple to make this (and many other features) work reliably.
 
I had this same issue, sort of (it wasn't just the spacebar for me it was ANY key), I posted a few comments/screenshots/videos looking for help on this forum. My 6S Plus is currently back on 10.3.3 to probably stay, but I had this issue in all versions of 10.x and eventually 11. Apple replaced my phone three times without luck. I had given up on using Quick Reply at all.

During the initial public betas of 11 I thought this issue was addressed, but I eventually clued in that I'd installed 11.0 using my more powerful PC rather than my old laptop when my issue vanished. I'd used the laptop for all my phones, from 3GS to 5 to 6S Plus on 9.x without issue, so I blamed iOS 10 for almost a year, was KICKING myself for upgrading from 9.3.5 and ruining my favorite iPhone ever.

I did a lot of trial and error and my theory worked out - installing from my laptop caused my buggy iOS 10 issue regardless of installed version. I installed the 10.3.3 .ipsw using my PC just before it was finished being signed and have only synced using it since. I can now use Quick Reply without issue instead of losing my text about 1 in 5-10 times. If anyone has an option to try an OS wipe and install from a different PC it might be worth a try. I exchanged 3 phones, reset all settings, didn't install apps etc etc and nothing helped. An install via my PC fixed my issue.
 
Last edited:
  • Like
Reactions: jrdatrackstar1223
So far, on 11.1 public beta 2, the issue hasn’t happened. I remember I would type and then try to swipe up from the space bar while typing and the quick reply would disappear and fly away.

When trying to do that on a quick reply on 11.2 public beta 2 it isn’t happening...
 
jrdatrackstar1223 said:
So far, on 11.1 public beta 2, the issue hasn’t happened. I remember I would type and then try to swipe up from the space bar while typing and the quick reply would disappear and fly away.

When trying to do that on a quick reply on 11.2 public beta 2 it isn’t happening...
Click to expand...
So it's still fixed on the later betas of 11.2?
 
I actually discovered on 11.1.2 that if you unlock the phone and try to swipe up while quick replying that it will dismiss it. When the phone is locked and trying to reply it will not do this. I think I may ha e spoke too soon when replying because I might have been seeing the “good behavior” while the phone was locked on 11.2 beta 2.

The way to test is to unlock the phone and try to swipe up while quick replying.
 
darrylcn said:
I had this same issue, sort of (it wasn't just the spacebar for me it was ANY key), I posted a few comments/screenshots/videos looking for help on this forum. My 6S Plus is currently back on 10.3.3 to probably stay, but I had this issue in all versions of 10.x and eventually 11. Apple replaced my phone three times without luck. I had given up on using Quick Reply at all.

During the initial public betas of 11 I thought this issue was addressed, but I eventually clued in that I'd installed 11.0 using my more powerful PC rather than my old laptop when my issue vanished. I'd used the laptop for all my phones, from 3GS to 5 to 6S Plus on 9.x without issue, so I blamed iOS 10 for almost a year, was KICKING myself for upgrading from 9.3.5 and ruining my favorite iPhone ever.

I did a lot of trial and error and my theory worked out - installing from my laptop caused my buggy iOS 10 issue regardless of installed version. I installed the 10.3.3 .ipsw using my PC just before it was finished being signed and have only synced using it since. I can now use Quick Reply without issue instead of losing my text about 1 in 5-10 times. If anyone has an option to try an OS wipe and install from a different PC it might be worth a try. I exchanged 3 phones, reset all settings, didn't install apps etc etc and nothing helped. An install via my PC fixed my issue.
Click to expand...


This is an interesting theory. I have tried installing iOS 11 from both my work laptop and my home touch PC. No matter how many times I've installed from scratch on iOS 11 this still happens. On top of that, this issue never happened to me on any version of iOS 10. That is crazy that people have had this problem since iOS 10. I will try perhaps to do a DFU restore instead of just a plain wipe and install from scratch.
 
I should add - mine were all DFU. Including the one that fixed my problem. iOS 10 was a MESS (half drawn calculator, all kinds of transient weirdness) before the eventual fix. Quick Reply still isn't perfect (message still vanishes when I resume typing if the screen dims as if it's about to auto lock during my reply) but it's MILES better than before.
 
  • Like
Reactions: jrdatrackstar1223
darrylcn said:
I should add - mine were all DFU. Including the one that fixed my problem. iOS 10 was a MESS (half drawn calculator, all kinds of transient weirdness) before the eventual fix. Quick Reply still isn't perfect (message still vanishes when I resume typing if the screen dims as if it's about to auto lock during my reply) but it's MILES better than before.
Click to expand...


Very interesting. I only experienced iOS 10 through the SE and the 6 and the only problems I ever had were sometimes the spotlight search wouldn’t be able to relocate my location and show close relevant results without resetting. Other than that (and shorter battery compared to iOS 9) my phone was perfect.

Interesting that a lot bugs ppl have with 11 were present in 10.
 
You're quite welcome. Hopefully you'll get your issues resolved too. The amount of stuff I blamed on and hated iOS 10 for is mind boggling, and now I wouldn't trade it and am glad I kept it on my 6S+.
 
  • Like
Reactions: jrdatrackstar1223
One thing i will say (although the behavior is the exact same as yours)....

Part of me is afraid this is more of an OS issue and intentional. Again, maybe I just never tried it on iOS 10 because it never happened to me, but if I open a quick reply box and just simply try to swipe up from the space bar slowly (as if trying to pull the control center in iOS 11 only from the keyboard), the entire "notification center" tray will swipe up along with it as if it is intended to do that.


I am trying to upload a video of it but for some reason Safari version is saying the screen recording doesn’t have the right extension type.



EDIT: Just had a friend try it on his iPhone 7 and the same issue happened. The issue occurs when your phone is unlocked and you perform a swipe up motion while typing on accident and it will dismiss everything. I just did a DFU restore with my iPhone SE and I can confirm the problem still happens with just swiping up while in quick reply.
 
Last edited:
I basically resolved it with the whole "more powerful computer applying a DFU restore" step. The only time I can make it occasionally happen now is by letting the screen dim by letting phone sit idle during a quick reply. And even then it's infrequent. Prior to my test it would absolutely dismiss next press if I let the screen dim, and it was 1/5 to 1/10 of the time when I was using it normally. For whatever reason the pull down quick reply that iOS 9x used never dismissed which is why I blamed iOS 10 for months. It turns out some combination of 10.3.3 and using my geriatric laptop broke it and it took a restore via PC via DFU to fix it. Sounds outrageous but as a test I managed to break iOS 11 (which had been fine when I went from 10-11 beta OTA) using my laptop. That's how I knew I had it beat. I did a final DFU restore while 10.3.3 was still signed and that was the end of it to this day.

Long story short - it's mostly been resolved that's why I suggested it here. I'm using QR again with pretty much impunity unlike before when I HATED (as my posts showed) the iOS 10 version of my phone.
 
Last edited:
  • Like
Reactions: jrdatrackstar1223
darrylcn said:
I basically resolved it with the whole "more powerful computer applying a DFU restore" step. The only time I can make it occasionally happen now is by letting the screen dim by letting phone sit idle during a quick reply. And even then it's infrequent. Prior to my test it would absolutely dismiss next press if I let the screen dim, and it was 1/5 to 1/10 of the time when I was using it normally. For whatever reason the pull down quick reply that iOS 9x used never dismissed which is why I blamed iOS 10 for months. It turns out some combination of 10.3.3 and using my geriatric laptop broke it and it took a restore via PC via DFU to fix it. Sounds outrageous but as a test I managed to break iOS 11 (which had been fine when I went from 10-11 beta OTA) using my laptop. That's how I knew I had it beat. I did a final DFU restore while 10.3.3 was still signed and that was the end of it to this day.

Long story short - it's mostly been resolved that's why I suggested it here. I'm using QR again with pretty much impunity unlike before when I HATED (as my posts showed) the iOS 10 version of my phone.
Click to expand...


Gotcha. Lucky you get to stay on 10.3.3! I am liking 11.2 but the battery is still terrible on my iPhone SE.
 
Yeah I'm hearing things are getting better but so far I'm resisting. That "no turning back" is a great incentive to stay on 10.3.3. Glad things mostly worked out for you guys who have updated though.
 
  • Like
Reactions: jrdatrackstar1223
You must log in or register to reply here.
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.
Top Bottom
Back