Move aside, A [?] — hundreds of users have reported yet another autocorrect bug that's been plaguing them since updating to iOS 11. This time, it happens when they go to type the (frustratingly common) word "it" into any text field. Once typed, the keyboard's predictive text bar shows "I.T" as a suggestion. Then, once the user hits the space key, the word "it" changes to "I.T" automatically, without the user ever actually tapping the predictive text suggestion. Many have taken to platforms like Twitter to voice their frustration:
Dear #apple iPhone team, as scary as it may seem, I’m actually trying to write “it” NOT( I.T )🗣🗣🗣
There’s always some malfunction with y’all 🙆🏽♀️Dear #apple iPhone team, as scary as it may seem, I’m actually trying to write “it” NOT( I.T )🗣🗣🗣
There’s always some malfunction with y’all 🙆🏽♀️— Kash da 👶🏽Sitter (@_4kashz19) November 27, 2017November 27, 2017
Users also report that unlike with other small iPhone bugs, this one sticks around even after attempting various troubleshooting techniques and device reboots.
If you're one of the iOS device users affected, here's how you can sidestep the issue until it's actually fixed by an update:
- Launch Settings from your Home screen.
- Tap General.
- Tap Keyboard.
- Tap Text Replacement.
- Tap on the little plus sign in the top right corner of the screen.
- Type "it" in both the Phrase and Shortcut fields.
- Tap Save.
If this work-around doesn't help (as some users claim that it doesn't) and you're really bothered by the bug, you can also choose to follow steps 1-3 and then toggle off both Predictive and Auto-Correction. It's definitely not ideal, but it will completely stop your phone from autocorrecting anything until the issue is officially addressed by Apple. Given that the company just included a fix for the A [?] bug in iOS 11.1.1, those affected are hopeful that a remedy for this new autocorrect annoyance will arrive soon.
Are you one of the individuals experiencing this autocorrect bug? Let us know if the text replacement solution has worked for you in the comments.
Tory Foulk is a writer at Mobile Nations. She lives at the intersection of technology and sorcery and enjoys radio, bees, and houses in small towns. When she isn't working on articles, you'll likely find her listening to her favorite podcasts in a carefully curated blanket nest. You can follow her on Twitter at @tsfoulk.
I have an iPhone X and iPhone 8+ both running 11.1.2. I don't have this issue at all.
Might be an issue with US English if you're using another type of English, not sure though. I don't use autocorrect so I can't test
I turn all of that crap off. Nothing more annoying than a tablet that thinks it knows what i want to say.
I turn it off, although it comes in useful for some people on touchscreen devices. Not sure why it exists on the Mac, I feel like it was just copied and pasted over for the sake of consistency.
The iOS keyboard has always and always will be a piece of junk. The Good news is that Google makes a perfectly serviceable replacement that doesn't have these bugs and has such 2008 features like swiping to type and a dark theme. Revolutionary really...
I mean swiping to type is something Swype came up with, not Google, and it's more personal preference whether it works for you or not. I don't like the swiping, but some people can't live without it, so the option would probably be nice. The iOS keyboard isn't a piece of junk, these autocorrect bugs have been the only problem with it for a long while. Other than that and not having the swipe feature (which for me personally I don't need) it's a perfectly great keyboard
Best to turn off autocorrect until they design it better. Changing words without any sort of confirmation process is idiotic.
Autocorrect is mainly for either slow-typers or people who can't spell. If you're not in those two categories, you're not in Apple's target audience for the feature and you can disable it. If you disable autocorrect, but keep word suggestions, then you can continue to use the word suggestions as a non-forced autocorrect, allowing you to choose the corrected word whenever you want
iPhone users using the stock keyboard* FTFY What about the bug on every keyboard that changes "ok" to "OK". It's a made up word, linguists don't know where it came from, so spelling doesn't matter. On top of that, "Is that ok?" looks less threatening in text than "Is that OK?" in my opinion.
If you look on any computer application or written form, you'll always see "ok" written as "OK". To be correct, you should either write it as "OK" or "okay", those are the two accepted forms, and I think all the autocorrection facilities in existence do the same thing by default.
No issues for me or anyone I know. Strange this seems to be a non issue issue. HEHEHEHE
That’s how auto-correct works — you type in your word and if the phone thinks it’s not a word, as soon as you hit the space bar, it corrects it with whatever is listed in the center part of your suggested words. Now, it still shouldn’t be autocorrected to I.T., but I’m just saying that’s why it happens that way when you hit the spacebar. Meanwhile, though, it’s not an issue on my iPhone 8 Plus with the latest iOS update.
If you want a "manual autocorrect", you can turn off autocorrect but keep the word suggestions. If you spell a word incorrectly, the "autocorrected" version will come up in the word suggestions, so you can still use the benefit of autocorrect without it being automatically used
Good option. I also found I had to do the it it one twice in settings for it to stick as the shortcut wasn’t saving first time around - when it didn't work I checked the settings and the phrase was there but not the shortcut. Two other things I’m getting are random auto capitalisations and I think the “smart punctuation” setting is messing with auto correct as the auto correct preview doesn’t use smart punctuation - I realise that doesn’t sound like it should make sense. :/
Get the best of iMore in in your inbox, every day!
Thank you for signing up to iMore. You will receive a verification email shortly.
There was a problem. Please refresh the page and try again.