iOS 7, iPad 4: keyboard problems with Shift key

Same problem here on iPhone 4S, iPad 3 and iPad 4 - seems independent of the keyboard language (native German speaker, too).

I'm usually typing quite fast so this may be a matter of timing. Never had this on iOS 6 or iOS 5.

As you said: a real show stopper!

I noted that exact same problem, and it's due to a change in how the shift key behaves. You usually write in kind of a "fluent rolling", so to capitalize a letter you press shift, then the letter to capitalize, and then in a rolling movement you release them the other way around, i.e. first shift, then the letter key. Until iOS 6 the shift state was hold until you release the actual letter key, even if you release the shift key fractions earlier. For iOS 7, the letter doesn't get capitalized if you release the shift key only fractions earlier -- the shift state is valid only whiule you press the shift key.

That is actually a showstopper. It's impossible to use the keyboard for fluent writing (which was surprisingly well possible before).

It's a bug. As many people as possible need to create a ticket to underline the urgency.

Just Updated to 7.0.2 - its the same as with 7.0.0

Still not fixed with iOs 7.0.3 :-(

Actually iPad has become unusable for me for writing eMails -- always taking a PC for that now again. Probably the opposite of Steve's dream, but they screwed it up completely and are ignorant towards users problems.

(just spent the same time as for writing just for editing capitals afterwards in this comment :-( )

Thank you Habitoti for describing the necessary change to the way that we need to type on ios devices to avoid the capital letter problem.

Holding the shift key fractionally longer solves the problem. But why oh why would Apple require users to fundamentally change the way they touch type by introducing a different keyboarding protocol like this? It is most unlike Apple to have us now have to consciously think about how to touch type all over again.

Intuitive operating systems are what make Apple so great. This keyboard problem is definitely not intuitive and it is driving me crazy.

Apple, you need to change the time weighting on the shift key in iOs 7.04.

Please, pretty please!

I opened a ticket for this quite a while before 7.0.3 already, but it's still in status "open". I am really impressed how few resonance this issue gets in the press. This is a complete showstopper for me. I don't write anything any longer on my iPad. Before iOS 7, I almost never used my MPB, but did all my mail etc. on the iPad. By now, it's vice versa again...

I've been noticing this issue since upgrading to ios7 myself. I thought it might have been a change in the keyboard or an issue with my ipad3. but I upgraded to an ipad air and the issue followed. one thing I didn't see here is whether you are getting a carriage-return/linefeed as well. that's what happens for me. and I discovered that if you tend to click the top of the right shift key, it will highlight the shift key but the <cr/lf> happens instead.

so you would see something like the following:

today, we learned that apple isn't infallible. there are times

i wish that weren't a true statement and

i lived in a perfect world, but there you have it.

I was able to reproduce some specific behaviour. Recently i needed to type an all capital abbreviation containing a whitespace. I started typing with one finger on the shift key. After three characters in capitals I typed a space still keeping my finger on the shift key as i would do on a physical keyboard. The following characters should I expect to be capitals again but they becam lower case although I was still holding one finger on the shift key.

So I think there is a problem with the shift state in combination with the spacebar. That makes touchtyping on this virtual keyboard annnoying for me ...

Habioti, is there a link to this ticket, where people could follow the progress? Thank you very much, Jens

It's a developer ticket (which can't be tracked by anyone else than the owner). Beyond that, it was closed by now as a duplicate, so at least it was somehow acknowledged ;-)

When it was closed, a reference to the duplicate ticket was given, but no one can't actually track that status now -- one of the ever lasting weirdnesses of the bug tracker system...

Regards, habitoti