Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
iOS 11 Bug: Typing 1+2+3 Quickly in the Calculator App Won't Get You 6
- Thread starter MacRumors
- Start date
- Sort by reaction score
Well... now I know why we don’t have an iPad calculator app. They still haven’t figured out how to get the iPhone one to work.
Why is this even "news"? It's not a calculation glitch, but rather as the article mentions a lag where the "+" after the 2 isn't acknowledged when typed quickly so instead of getting "2+3" the "+" gets omitted and you get "23" which when added to the "1" gives you "24". Typing in normal speed will allow for the lag to "catch up" and you'll get 1+2+3 = 6. I can even seen "23" on the screen before I press "=" so I know something isn't right and I can correct it.
I would guess this is whats taking so long... it’s not a calculator bug per se, it’s a bug in the OS code. When they fix the underlying issue, it will solve this type of input blocking issue in a variety of different places, not just calculator.
Fixing this should have been a higher priority
I guess Apple was too busy with real-time facial emoji's and and high-quality selfies...
Because we - the users - don’t give a crap if it’s a calculation error or an animation error, especially in such a simple project that was working perfectly. If I do 1+2+3 I expect to have 6 as a result. I don’t give a crap why it’s giving me a different result. Don’t try to minimize this.
Hang on.... I just looked for the calculator on my iPad and it doesn't have a calculator app built in?
Never even noticed! Is this true for everyone?
*head explodes*
Never even noticed! Is this true for everyone?
*head explodes*
A “computer replacement” that can’t compute natively
Why would I be interested in reading about issues with the Pixel phones on a Macrumors website?
Ha ha I just tried this for kicks on a 5C with iOS 10...
Built-in calculator: Yes, I get 24...
PCalc Lite: No, I get 6...
Getting a result other than 6 for 1+2+3 is the very definition of a calculation glitch. I type at a normal speed, but I don’t type slow enough to avoid calculation glitches in calculator.
Apple will fix it, but it’s been too long already.
Apple needs to understand if they want to be health, financial, and home/iot hubs and have iPads be taken seriously as a productivity tool, they need to increase what they think is acceptable quality levels in software.
Ios11 should have never shipped in this state. And the problem is until some place like the Wall Street Journal calls them out for their shoddy software quality and lethargic innovation rates in cloud, AI and software, nothing will change.
Ios11 should have never shipped in this state. And the problem is until some place like the Wall Street Journal calls them out for their shoddy software quality and lethargic innovation rates in cloud, AI and software, nothing will change.
Everyone knows that its not a real calculator unless it does reverse polish notation, so who cares, its just another toy for the kids.
Fairly pitiful response seeing as how this has been reported on since the 1st iOS 11 beta. They ignored it for months.
A bug in the built-in Calculator app in iOS 11 is getting some major attention this week, despite the fact that it's been around since iOS 11 was in beta testing.
At issue is a calculator animation that causes some symbols to be ignored when calculations are entered in rapid succession. You can try it for yourself: Type 1+2+3 and then the equals sign into the Calculator app quickly.
Due to animation lag introduced when adding two or more numbers together, your result is more likely to be 24 than 6.
The same goes for many other calculations -- the Calculator ignores some inputs unless you're entering numbers slowly enough to account for the light-up button animations that highlight the keys that are being pressed. Symbols do not register when tapped while a number button is still highlighted, resulting in incorrect calculations if you're inputting numbers quickly. Reddit user cplr describes the problem:There are hundreds of complaints about the problem on reddit this week, but it's an issue that's been discussed on the MacRumors forums since the iOS 11 beta testing period. Throughout the beta testing process, the animation lag was not addressed, nor has it been fixed in any of the iOS 11 updates released so far. It's also still present in iOS 11.1.
Some users have experienced similar issues when using older versions of iOS, but the animation lag is noticeable enough in iOS 11 to make the Calculator nearly unusable when attempting to make rapid calculations.
Apple seem to be aware of the issue, because as The Loop points out, Apple employee Chris Espinoza says more than 70 people have filed a Radar report on the bug, alerting Apple to the problem. With it receiving so much attention, we could potentially see a Calculator fix in the next iOS 11 update.
In the meantime, iOS users who need a reliable alternative can use third-party apps like Calcbot and PCalc.
Article Link: iOS 11 Bug: Typing 1+2+3 Quickly in the Calculator App Won't Get You 6
I've had iPads for YEARS since the first one. Crazy.
A “computer replacement” that can’t compute natively
I mean I never missed it clearly. Does seem maybe a little strange though
No, Apple can do many things simultaneously. To my mind, this was simply under-prioritized.I guess Apple was too busy with real-time facial emoji's and and high-quality selfies...
We have reinvented Mathematics which is 10000 years old. It took us courage to redesign it!
A bug in the built-in Calculator app in iOS 11 is getting some major attention this week, despite the fact that it's been around since iOS 11 was in beta testing.
At issue is a calculator animation that causes some symbols to be ignored when calculations are entered in rapid succession. You can try it for yourself: Type 1+2+3 and then the equals sign into the Calculator app quickly.
Due to animation lag introduced when adding two or more numbers together, your result is more likely to be 24 than 6.
The same goes for many other calculations -- the Calculator ignores some inputs unless you're entering numbers slowly enough to account for the light-up button animations that highlight the keys that are being pressed. Symbols do not register when tapped while a number button is still highlighted, resulting in incorrect calculations if you're inputting numbers quickly. Reddit user cplr describes the problem:There are hundreds of complaints about the problem on reddit this week, but it's an issue that's been discussed on the MacRumors forums since the iOS 11 beta testing period. Throughout the beta testing process, the animation lag was not addressed, nor has it been fixed in any of the iOS 11 updates released so far. It's also still present in iOS 11.1.
Some users have experienced similar issues when using older versions of iOS, but the animation lag is noticeable enough in iOS 11 to make the Calculator nearly unusable when attempting to make rapid calculations.
Apple seem to be aware of the issue, because as The Loop points out, Apple employee Chris Espinoza says more than 70 people have filed a Radar report on the bug, alerting Apple to the problem. With it receiving so much attention, we could potentially see a Calculator fix in the next iOS 11 update.
In the meantime, iOS users who need a reliable alternative can use third-party apps like Calcbot and PCalc.
Article Link: iOS 11 Bug: Typing 1+2+3 Quickly in the Calculator App Won't Get You 6
This is a bug that never should have made it to release. Hell, it never should have made it to the SECOND BETA.
1) It was reported almost immediately.
2) It's obvious and easy to reproduce. Some bugs are a total bitch to repro; this one was trivial.
3) It's in a feature that a lot of people use regularly.
4) The bug causes incorrect results. Crashes, graphical glitches are merely annoying. Incorrect results can be catastrophic depending on what's being calculated.
It's downright embarrassing that this bug made it past iOS 11.0 beta 1. It's absolutely ridiculous that it made it into release. It's the biggest WTF ever that it's still in iOS 11.1 beta 5. What the hell, Apple?
EDIT: I also wanted to add that I'm glad this bug is getting more attention. Apple deserved to be embarrassed over this. And it might actually get fixed now since it seems they didn't care before.
1) It was reported almost immediately.
2) It's obvious and easy to reproduce. Some bugs are a total bitch to repro; this one was trivial.
3) It's in a feature that a lot of people use regularly.
4) The bug causes incorrect results. Crashes, graphical glitches are merely annoying. Incorrect results can be catastrophic depending on what's being calculated.
It's downright embarrassing that this bug made it past iOS 11.0 beta 1. It's absolutely ridiculous that it made it into release. It's the biggest WTF ever that it's still in iOS 11.1 beta 5. What the hell, Apple?
EDIT: I also wanted to add that I'm glad this bug is getting more attention. Apple deserved to be embarrassed over this. And it might actually get fixed now since it seems they didn't care before.
Funny how the most basic app on this OS is failing this hard compared to the newer more complex features and APIs added across everything else.
100% Agreed... maybe it's due to Apple having other priorities? Like this type of priority: Apple’s ‘spaceship’: more than a year to approve a door handle, and toilets like iPhones, report says
BUT it's NOT a calculation glitch because it's not 1+2+3 = 24. What you're getting is 1+23. If I typed 1+2+3 and that's exactly what was recognized and I get 24 then yeah that's a calculation glitch. All it is is the "+" sign isn't being picked up when quickly typed after the 2. It's a moot point if typed 1/2 a second slower.
Holy crap - I was adding up all the km in my vehicle logbook for my tax return a couple weeks ago and was ready to throw my iPhone at the bloody wall by the end of it, has no idea this was an issue that has been well-known by Apple for so long and like so many other bugs they just haven't got around to fixing it