4 ms·
It’s a really hard bug to run into - you have to get the bad Unicode I-that-isn’t-an-I in your autocorrect dictionary somehow (for example by having someone els
by djrogers 9y ago
It’s a really hard bug to run into - you have to get the bad Unicode I-that-isn’t-an-I in your autocorrect dictionary somehow (for example by having someone else text it to you multiple times), then this character shows up as an autocorrect suggestion. If you’re in messages, it still shows the fake I as an emoji, so you dont see the problem sometimes.
- c3534l 9y agoSo this bug is contagious?
- thsowers 9y agoI think overall this release might lead some to believe that Apple is spending less time on QA. For instance, bugs that are much easier to run into, like the calculator bug[0] still somehow made it into production [0]: https://news.ycombinator.com/item?id=15538666 https://news.ycombinator.com/item?id=15538666
- saagarjha 9y agoThey're easy to demonstrate. I'm not sure I'd qualify them as easy to run into. Generally when using the calculator (if I do use it all!) I'm not focusing on typing very fast.
- plorkyeran 9y agoThe iOS 10 version of the calculator app has a nearly identical issue, so it's not a very good example of things going downhill in 11.
- bpicolo 9y ago> for example by having someone else text it to you multiple times This one is super widespread. I don't believe I had anybody text it to me before it showed up for me. Over-the-air model update perhaps? Could have been a virus-spreading situation but it seems like something else.
- andygates 9y agoStuff that people send you ends up in your dictionary? That seems problematic.