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.
Apple Apologizes About FaceTime Bug, Software Update With Fix Delayed Until Next Week
- Thread starter MacRumors
- Start date
- Sort by reaction score
Absolutely agree that Apple's processes need to change. They need to ditch the waterfall software development method on products and stop being a black box where feedback goes in and the only thing that comes out is a shiny new product once a year.
Blame the customer for not participating in the beta or already customers are doing beta?
Nope, she was outside with the iPhone, the Apple watch uses bluetooth to communicate with an iPhone, too far away to be able to.
You probably read that story somewhere, it's from a Turkish publisher and has been debunked.
I'm starting to wonder if this wasn't a bug at all, but an intended, intentional feature for governments and the like, as a potential way to catch terrorists etc. Think about it - hitting the power button on the incoming call alert ACTIVATES the video, ALL WHILE still showing the call as not accepted. It just doesn't make sense, and when things don't make sense, there is usually a reason for it.
Come on just admit it. You play around with poop emojis when nobody else is in the room.
No, when things don’t make sense it’s because of entropy. **** happens. Not everything is a conspiracy.
"Slowed down" as opposed to unveiling our defective processors that shut off the phone at all various times regardless of battery, you mean. I had several defective devices and they would shut off at 88%, 41%, 13%, 65%, wherever it felt like it. The phone would just turn off, and then not boot back up until plugged back into an actual power source.
The throttling was to mask the defective manufacturing of millions of devices. They still haven't answered to that properly, IMO and I hope they lose every battery lawsuit on the books. They should. It was criminal behavior - absolutely criminal.
Works too well as a surveillance tool to be a bug which usually results in a crash, respring or hang. Coincides with forcing Face ID since close ties with Chinese government police state employing country wide face recognition on its citizens. Same reason Apple moved citizen iCloud data to Chinese government controlled servers.
I thought it was a mistake until I realized that when using this bug and adding yourself, if the user on the other end hits the power button (which is common to do to decline a call), only *then* does it activate the video.
Why would a bug, already in process, *further* bug-a-fy itself by allowing the video to be enacted once the power button is hit?
It really doesn't make sense. Think about it. Think of the implications of what this bug could do for law enforcement or anyone with nefarious motives, really.
That's the thing, it WASN'T dealt with in accordance with Apple's procedures. The team the bug was reported to is supposed to deal with security issues directly. Instructing her to file a Radar goes AGAINST Apple's procedures for this particular team.
Are you for real? The team they specifically created for the public to report critical security flaws, when presented with such a flaw, gave the person reporting it the brush off. And you think that was the right thing to do? Even though Apple themselves admitted that they need to improve the process?
While I initially thought that someone's head needed to roll for this, I'm starting to not care about that as much. And if someone does lose their job, I think it would be terrible for Apple to say so unless that person is a member of the executive team. BUT, what I do want from them is disclosure on HOW they are going to address these flaws in their procedures. There have been a disturbing number of critical security vulnerabilities in Apple's software over the last year and a half or so. A pattern is emerging here, and Apple needs to convince us that they're really taking it seriously.
Issues like this are called edge cases. When Apple was creating the requirements for the feature they should have documented use case scenarios which included what users could and could not be added to the call and when. A good QA engineer will take that documentation and ask "What happens when I intentionally DON'T follow what this says?" They will then create and document test cases that not only test the intended functionality, but also test for unintended functionality. Yeah, no QA engineer will be able to cover everything, but this does fall within the realm of things that I could envision a QA engineer coming up with.
I'll say this much. I got a FaceTime call from an unknown number on New Year's Eve. I now strongly suspect it was related to this issue.
Well at least one of the cases is from a lawyer who says this was used on his own phone while he was discussing a case and as a result attorney-client privilege was breached. He wouldn't be making such a detailed claim if he didn't have something to back it up with.
Obviously you've never written any code of significance. It's easy, even trivial to introduce a bug that doesn't cause a crash or hang. It doesn't require a conspiracy to botch an "if" statement that turns video on when a button is pressed instead of turning it off.
It's a bug. It's a flaw in the logic. Sure, there could have been some grand conspiracy, but anyone who has written any substantial code knows that it's very easy to do something dumb (or brilliantly convoluted) and get totally unexpected behavior. It'd take more than imagining that someone might use this for nefarious purposes to suggest that it's anything more than a mistake.
Watch out -- we got a software dev badass over here!
Yeah, we're all pissed, Buddy, but don't assume to know the first thing about how complex consumer software systems are developed.
The software you're talking about isn't just a "Hello World" program but incredibly complex. It has millions of lines of code and even with automation testing there's a good chance you're missing a serious bug. If there isn't, big companies like Google and Microsoft etc wouldn't have any of those bug bounty programs for outsiders to find the bugs. They'd rather just employ more people for this stuff but then again it's "practically" impossible to test and make a perfectly bug free software regardless of what you do.
Just because Apple designs their own devices doesn't mean they create their own products and the number of variables. And this only shows your very limited knowledge about the complexity of the technology involved in making your device, Apple or otherwise.
Android's Play Store itself distributes hundreds of apps that have been reported to contain malware. The Play Store is completely in Google's control unlike Android OS itself and it doesn't even involve other manufacturers for chips or screens etc. I'd like to hear your perspective and excuse for Google's mistake when there's rarely any report of the same happening in Apple's App Store?
So you agree the same issue exists in android? Except on android there is no “slow down”, the phone just shuts off.
Not a chance, stop making excuses and accept Apple places profits and share price above quality control. Don’t give me the spin about complex either. Because last time I checked Apple has billions and billions tax free to spend on employees of the highest calibre to code properly. And as I stated IT designed the hardware the OS runs on.
Stop deflecting from the point of my post too by claiming it has mistakes.
[doublepost=1549048656][/doublepost]
See above, you’ve just made an excuse and nothing more.
And erm, Apple does create its own devices, you’ve contradicted yourself there?
Right, continued use of the public as their beta testers. People continuing to blindly defend Apple doesn’t help any of us.
What happened to Apple is that the software and hardware has evolved exponentially over the years and is a lot more complex than it was before. It's like comparing a kids' toy car to that of a Ferrari. They're both technically cars so why would replacing a side mirror of a Ferrari costs more than the toy car itself?
[doublepost=1549048873][/doublepost]
Designing and manufacturing are not the same pal.
And if you're so sure about your rational for a bug in the software, why haven't you answered my question about Google Play Store?
"Heads will ROLL!!!" Bugs result from fault-lines in the process, not individuals. But more to the point, your disciplinarian concept of management is so flawed it would lead to the demise of a company within a year. Every single engineer would be out looking to move elsewhere.
Another excuse by the blindly defending Apple. To use your analogy, as the hardware evolves so should the QC and testing to equal the advancements. One shouldn’t be lagging behind the other. That’s just stupid.