Something so heinous that you didn't even notice it until it was already fixed.
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.2 Beta Fixes Calculator Bug Causing Incorrect Calculations when Numbers Are Rapidly Entered
- Thread starter MacRumors
- Start date
- Sort by reaction score
Exactly, this would have been a great method of leveraging the App Store to resolve individual iOS embedded apps when needed. No need to wait for a major iOS release to get this fix included.
The assumption there would be that the fix was simply something in the app itself and didn't involve something outside of it (like some system library/framework or something else of that nature).
Wow fixing a calculator in 3 months with the assets of a trillion dollar software company sounds challenging. Amazing how they are even able to get iOS to boot up. Well the way things are going, they may not be able to do so in the near future...
Realistically speaking it was being discussed here quite a bit before an actual article was put up: https://forums.macrumors.com/threads/calculator-app-is-unusable.2078357/ (and mentions of the issue go back even further into iOS 11 beta stage).
[doublepost=1509388467][/doublepost]
We can complain about the realities of the software development lifecycle, similar to complaining about the fees we have to pay for this or that here and there, and many other things in life basically, but none of that really changes the reality of things being what they are.
Last edited:
All the money in the world doesn’t make software projects suddenly abide by different rules, so that part is irrelevant.
[doublepost=1509388712][/doublepost]
It happens occasionally. Probably just a matter of hours, days at most, until 11.1 final. I think there was a time where 8.2, 8.3 and 8.4 builds were available in parallel.
MacRumors reported on this 2 whole days after it broke on Twitter and then went big on Reddit. They were far far behind the initial reports.
It was being discussed here at MR quite a bit before an actual article was put up: https://forums.macrumors.com/threads/calculator-app-is-unusable.2078357/ (and mentions of the issue go even further back into iOS 11.0 beta discussion threads).
Makes you wonder why it always has to come to this first for certain seemingly obvious issues to be resolved.
No, it was reported multiple times through official channels. One of the Apple guys tweeted about it; I can't remember if it was 50 or 80 times, but it was up there.
Edit: Here we go… https://twitter.com/cdespinosa/status/922870769373265920
Last edited:
It might not have come to that given that this was reported and was known sometime before all of that and quite likely was addressed before all of that given that this beta was already something that was going through internal testing and getting ready to be released to developers (and public beta testers) for at least a little while now.
Was there anyone else that thought of the Therac-25 with this problem?
https://en.wikipedia.org/wiki/Therac-25
"The failure only occurred when a particular nonstandard sequence of keystrokes was entered on the VT-100 terminal which controlled the PDP-11 computer: an "X" to (erroneously) select 25 MeV photon mode followed by "cursor up", "E" to (correctly) select 25 MeV Electron mode, then "Enter", all within eight seconds.[6] This sequence of keystrokes was improbable, and so the problem did not occur often and went unnoticed for a long time.[4]"
That’s sad.
I have been using it to convince my bank that their interests rate calculation was wrong. You know, math doesn’t lie.
I have been using it to convince my bank that their interests rate calculation was wrong. You know, math doesn’t lie.
This could have been fixed during the iOS 11 beta cycle or during the beta cycle of 11.1 at the latest. The question is why it apparently didn‘t get Apple‘s attention for so long (like so many other things that are reported only to be ignored)
And this whole time I thought Apple was reinventing Mathematics
I miss the 60's.
What we are saying is that it would have been nice if it was fixed sooner, or wasn't even there to begin with, but it's harder to make a call as far as when it could have been fixed not knowing the details of it all (on technical side, as well as business side as well, given that it all plays a role). For example, the assumption there would be that the fix was simply something in the app itself and didn't involve something outside of it (like some system library/framework or something else of that nature) that might have required more changes and more testing. It also doesn't factor in other business needs as far as other things that are being worked on and timelines and and all of that. Not having something addressed sooner doesn't necessarily mean that it's being ignored.
It's funny, way back in the iOS 7 WWDC announcement, I could have sworn they mentioned a feature to update individual apps that were integrated with iOS. I guess that didn't get off the ground. There was also a feature that when you cleared a notification on one devices, it cleared them on all.
There were also panoramic wallpapers, which never made it to final.
This is ridiculous. This should be a hot fix, not 11.2.. lol