iOS 11.2: Calculator bug 1+2+3=234

#1

Post by vijaysr » Sun, Dec 03, 2017, 4:46 PM UTC

I was able to reproduce calculator bug on iOS 11.2 on an iPhone SE. See a short video in link for demonstration. I used only one finger to tap. I was able to reproduce it multiple times.

https://www.dropbox.com/s/rurojjf0bwjvuih/File%20Dec%2003%2C%208%2032%2028%20AM.mov?dl=0

Re: iOS 11.2: Calculator bug 1+2+3=234

#2

Post by arooaroo » Sun, Dec 03, 2017, 7:39 PM UTC

Wow. I’m just trying to do 1+2+3= and I’m consistently getting 24.

Re: iOS 11.2: Calculator bug 1+2+3=234

#3

Post by taf2 » Sun, Dec 03, 2017, 7:42 PM UTC

arooaroo wrote: post #2

Wow. I’m just trying to do 1+2+3= and I’m consistently getting 24.

Me too

Re: iOS 11.2: Calculator bug 1+2+3=234

#4

Post by graeme » Sun, Dec 03, 2017, 7:43 PM UTC

Also occurs for me on 11.1.2

Re: iOS 11.2: Calculator bug 1+2+3=234

#5

Post by mbell » Sun, Dec 03, 2017, 7:43 PM UTC

arooaroo wrote: post #2

Wow. I’m just trying to do 1+2+3= and I’m consistently getting 24.

It's a UI bug, if you type fast it misses a `+` input so is performing 1 + 23.

Re: iOS 11.2: Calculator bug 1+2+3=234

#6

Post by lambada » Sun, Dec 03, 2017, 7:44 PM UTC

I can get 1 + 2 + 3 = 24. That appears to be because the second '+' action doesn't register if it's still doing its click animation.

I cannot reproduce 234 though.

Re: iOS 11.2: Calculator bug 1+2+3=234

#7

Post by jonmagic » Sun, Dec 03, 2017, 7:44 PM UTC

arooaroo wrote: post #2

Wow. I’m just trying to do 1+2+3= and I’m consistently getting 24.

I’m getting the same on 11.1.2

Re: iOS 11.2: Calculator bug 1+2+3=234

#8

Post by jmkni » Sun, Dec 03, 2017, 7:49 PM UTC

I don't think this is new, I remember it being mentioned on Reddit earlier this year

Re: iOS 11.2: Calculator bug 1+2+3=234

#9

Post by teilo » Sun, Dec 03, 2017, 8:12 PM UTC

This was a problem on all iPhones until 11.2. On my 7+ the problem went away on 11.2, and no matter how fast I tap buttons, I get 6.

If you hit the buttons more slowly, it will register correctly. It shouldn't happen on any phone, though, and it is ridiculous that the problem is still around 2 major revisions later.