MacRumors ran their story 2 days AFTER it went viral on Twitter and then Reddit. MacRumors wasn't the reason this got visibility.
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
MacRumors ran their story 2 days AFTER it went viral on Twitter and then Reddit. MacRumors wasn't the reason this got visibility.
I think it's more to do with Apple's sloppy and frustrating input-blocking during/following animations that's been the cornerstone of i[nput-blocking]OS since 7.0.
It's more urgent in the case of the calculator as it's far more difficult to tell when it's blocked an input than when you're navigating, for instance.
As of iOS 11.2 Beta 1, instead of an incorrect value you see the text
... Buffering ... Buffering ...
... Buffering ... Buffering ...
You keep saying that but there are countless calculator apps in the app store that work fine with the framework, API's, all the items you have mentioned. Sooo if theirs was a stand alone app, it stands to reason an app update/fix could have solved this, no?
Looks like people submit more bugs on macrumours website than Apple internal Bug tracking Tool. What a shame! what a quality control.
Not it's not you. Apple seems to only have the capability to work on the top few things only. Everything else just sits in the dustbin until the negative publicity reaches unacceptable levels. If you want something out of the new Apple you have to generate tons of negative PR. Users, don't matter, but PR that is a different issue. They don't have all of those high paid marketing executives for nothing.
[doublepost=1509396011][/doublepost]
Cook took over, now it is just about on-time delivery, working or not. Hit the deadline with no accountability. Cook doesn't scare anyone, he is a nice guy. So whatever happens, happens. No big deal. Much nicer work environment than the Jobs environment. No one wanted to let Jobs down, if possible. With Cook, no big deal. Hit the delivery date and all is golden, don't sweat the details.
Last edited:
In a situation like that that would likely be the case. The assumption there would be that they are all using the same type of things and the fact that the other ones aren't having this issue means that it's all down to the app itself. The underlying point is that we don't know what's involved there exactly, and we can suppose that it's this or that, but it doesn't necessarily mean that's the case.
Correct. And this was identified and reported during the early stages of beta testing this last summer. The fact that Apple could not make this fix (and many other simple reported bugs) before the public release speaks volumes about their workload. They are juggling too much.
The good old days with Steve Jobs when releases like iOS 4 came close to actually almost crippling some iPhone models to the point that Steve had to even address the issue and promise that it will be taken care of in a software update. Yes, those were the days of trouble/bug/issue-free Apple with amazing quality control.
[doublepost=1509396277][/doublepost]
It's been around here earlier than that, just not in a form of a front page article.
[doublepost=1509396368][/doublepost]
It's one possibility. Others can be that they prioritized it lower than other things, or it involved changing more than something small and needed more time and attention, the other being that it slipped through the cracks for a while, which unfortunately also happens in all kinds of companies when it comes to all kinds or things.
[doublepost=1509396638][/doublepost]
Based on the fact that this was submitted to Apple and has been known by Apple for for some time?
Last edited:
So after 10 developer betas, public release, 3 updates, 5 .1 betas and 1 .2 beta, Apple fixes something that shouldn’t have been broken in the first place. Praise be!
Some praising Apple for updating, they shouldn’t be getting away with releasing an unfinished product on circa £700-1000 devices!
Some praising Apple for updating, they shouldn’t be getting away with releasing an unfinished product on circa £700-1000 devices!
For those who do not test Betas (like myself) and do not know the schedule, it's helpful to know what will most likely or probably be addressed in the official releases.
Have a nice evening.
11.1, which includes the fix, will probably come out any day now, possibly later tonight.
[doublepost=1509397985][/doublepost]
I do the know about “too much”. It’s a question of prioritization. No major piece of software ships without bugs or known issues. Priority is a function of effort and gain, and either this took a while or the gain was deemed too low to make the cut for an earlier release.
[doublepost=1509398065][/doublepost]
Ah yes, the golden days of iTunes 2.0.0, the installer of which could wipe your hard drive.
Apple are vastly richer now than they were at the time of iOS 4. Why can't they afford a more or better OS developers?
Or perhaps the problem is yearly iOS and macOS updates from the one OS team at Apple. Lengthen the update schedule to 18 months. Considering the pace of change from the iPhone 6 to the iPhone 8 then hardware is already on what amounts to an 18 month schedule. It would give OS developers time to polish the new OS before release instead of introducing what is essentially a beta and polishing it to a final release over several 0.x updates.
Is that kind of like if you get more and/or "better" women you'd be able to produce a baby in less than 9 months?
Congrats guys, this is a triumph for everyone that got involved in reporting, recording youtube videos, sending bug reports, making fuss in social media etc. Great job, keep up the good work.
By the way, thanks to our work, we helped this issue gain traction and avoid more years of Apple neglecting it, as it was reported this issue was resurfacing on and off since iOS9/iOS10. It took youtube, reddit, macrumors, twitter and mainstream media creating turmoil for Apple to finally take action.
By the way, thanks to our work, we helped this issue gain traction and avoid more years of Apple neglecting it, as it was reported this issue was resurfacing on and off since iOS9/iOS10. It took youtube, reddit, macrumors, twitter and mainstream media creating turmoil for Apple to finally take action.
There are some potential issues with that. First is that there are plenty of real world scenarios that are hard to test for even with more time and people so there will still be things that will surface nonetheless and people will talk about why don't they take 2 years to release something or something else along those lines. Another one, and perhaps more important one, the market seems to more or less demand something fresh/new/different (in one form or another) pretty much as quickly as possible. Apple might be able to improve some quality with additional time, but in the process might lose out on some consumers as there will be plenty who are going to be complaining how things look the same and they are bored and Apple doesn't care about them and isn't giving them anything new/different.
Project management doesn’t scale that way.
I don’t think the length makes any difference. The synchronization, however, might. All those releases are roughly in the same timeframe, always with the first pre-release at WWDC and the final whenever the new iPhone comes out (slightly later for macOS). This has some benefits, but also creates pressures that may not otherwise be prudent.