Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
I was curious if something like this happened on Android and what their response was. Also, did the media post the method of doing it online. Well low and behold! They did have a similar issue but also giving root access to unauthorized apps. Once obtained they could turn on cameras and microphones to record and send info anywhere with an internet connection. This was mentioned in passing in December. I hope this was just another bug doing the same but all the way back in 2011 they had a bug doing exactly this. https://nakedsecurity.sophos.com/20...sions-glitch-allows-eavesdropping-data-theft/
 
Very well said! Under Jobs there were major consequences. Under Cook, well I’ll refrain from saying what I think happens under Cook. No I won’t. Little to nothing. LOL
What were the major consequences under Jobs, out of curiosity?
 
Even though this FaceTime bug was a mistake, it shows how easy it is to install an eavesdropping feature on products unknown to users. There is no doubt that the NSA/CIA works closely with Microsoft/Google/Cisco/etc and is using devices & software for this purpose if they want to target individuals or corporations (btw, hence the fight against Huawei).
 
Meanwhile, Google, Facebook, Amazon, etc are boldly and obviously stealing EVERYTHING from you and nobody bats an eye.

well yeah they don't claim to be the godly standard in security.

apart from the fact that your agree for your data to be used in exchange for their services
 
  • Like
Reactions: pat500000
Even though this FaceTime bug was a mistake, it shows how easy it is to install an eavesdropping feature on products unknown to users. There is no doubt that the NSA/CIA works closely with Microsoft/Google/Cisco/etc and is using devices & software for this purpose if they want to target individuals or corporations (btw, hence the fight against Huawei).
No they don’t. They may embed employees in the hopes of sneaking backdoors in, but there is no way these companies willingly work with spy agencies.
 
You still don't get how things work here. The chips are borrowed from Intel and Qualcomm not Foxconn. Just cuz you're misreading my statement doesn't mean it's what I said.

And I never said Google has anything to do with this article. Just that I'd like to hear your thoughts on the matter since it's a similar case. You're saying since Apple does their own software for their custom designed hardware it should be bug free before they're delivered while I'm saying introduction of new features into an existing software would be grounds for potential bugs that can be overlooked regardless of how huge your testing team is.

I’ll reply again. Firstly I am not going to give any of my opinions on Google as this story is not about them.

Secondly, are you claiming that this FaceTime bug is caused by the 4G modems Apple buys? Because I’m not sure what they have to do with bugs in iOS.
 
Last edited:
  • Like
Reactions: pat500000
Also delayed: AirPower, AirPods 2, etc.

Just a question for myself... did I miss an announcement or did the community just decide that there were supposed to be new AirPods and then excoriate Apple for there not being new AirPods? It's not something I'd ever buy anyway but following it is amusing.
 
but is that really the fault of Apple or of the jackass who decided to try it with the attorney's number. just because you CAN kill someone with a gun doesn't make it okay to actually do it. and the law doesn't punish gunmakers because someone used a gun to commit murder

and what about the woman who released the information for her 15 minutes of fame. had she not been greedy for attention it might have been weeks before anyone else even knew this bug existed. well after Apple fixed the glitch, released an update and perhaps barred anyone without the update from using Group FaceTime or perhaps even FaceTime in general so that they could make sure no one else was affected by the bug

Your response commits two logical fallacies. First, you’re creating a false dichotomy.
This line of reasoning fails by limiting the options to two when there are in fact more options to choose from. Sometimes the choices are between one thing, the other thing, or both things together (they don’t exclude each other). Sometimes there are a whole range of options, three, four, five, or a hundred and forty-five. However it may happen, the false dichotomy fallacy errs by oversimplifying the range of options.
You’re implying that the only options are that people sue Apple OR they sue someone else. The option exits that ALL the parties you mention get sued. By saying “Well why don’t we sue so-and-so,” you’re not giving a reason why someone should NOT sue Apple.

The second fallacy you commit is creating a red herring.
A “red herring” is a distraction from the argument typically with some sentiment that seems to be relevant but isn’t really on-topic. Typically, the distraction sounds relevant but isn’t quite on-topic. This tactic is common when someone doesn’t like the current topic and wants to detour into something else instead, something easier or safer to address. Red herrings are typically related to the issue in question but aren’t quite relevant enough to be helpful. Instead of clarifying and focusing they confuse and distract.
I fail to see the point of bringing guns into the discussion other than to distract from the main topic. I shouldn’t have explain to you the differences between guns and FaceTime.

Source: https://thebestschools.org/magazine/15-logical-fallacies-know/
 
Last edited:
I fully accept the apology. And I'm looking for a statement from the CEO along the lines of "The team responsible for the bug is no longer with the company." But I don't see it. This is weak leadership, Tim. You need to regain our confidence and trust.
I think it is absurd to fire the team for failing to find a bug that is triggered outside of normal usage. If you were to institute that kind of requirement, Apple would cease to function in software development.

We know some details. We don't know all the details. From what I do know at this point in time, Apple has acted in a prudent and reasonable manner with this incident.
 
I think it is absurd to fire the team for failing to find a bug that is triggered outside of normal usage. If you were to institute that kind of requirement, Apple would cease to function in software development.

We know some details. We don't know all the details. From what I do know at this point in time, Apple has acted in a prudent and reasonable manner with this incident.
Did anyone at Microsoft get fired when a recent windows 10 update deleted user files? Firing is not the norm except for malfeasance or repeated gross incompetence.
 
  • Like
Reactions: Apple_Robert
I’ll reply again. Firstly I am not going to give any of my opinions on Google as this story is not about them.

Secondly, are you claiming that this FaceTime bug is caused by the 4G modems Apple buys? Because I’m not sure what they have to do with bugs in iOS.

That was just my argument for the part where you said Apple makes both the hardware and software. I’m just saying there are parts made by companies other than Apple in an iPhone.
 
I fully accept the apology. And I'm looking for a statement from the CEO along the lines of "The team responsible for the bug is no longer with the company." But I don't see it. This is weak leadership, Tim. You need to regain our confidence and trust.

You are free to stop buying Apple products if you think you no longer trust the company.

Sacrificing a scapegoat to appease the rabid hordes is precisely the last thing I expect any company to do in such an event. I don’t need anyone to be fired. Mistakes happen, it will soon be fixed, the sun will still rise in the east, and life goes on.

Apple doesn’t need to do anything of the sort you are suggesting.
 
  • Like
Reactions: I7guy
This bug must be particularly tricky if they have to delay the fix until next week. You'd think it'd be a simple fix, but I guess not.


They'll take any excuse to rage against Apple's current leadership, honestly.

It's probably also just them being careful to not bring in other issues. I've been in situations like this where you need to get the fix out the door ASAP but in that sort of crunch mode you end up risking making some really silly mistakes and causing further issues.
 
No. Reading it in the full context of the rest of the apology, they are saying that the bug report didn’t even get to the engineers, and they need to improve the process they use to escalate bug reports from the public.
Are you sure? Then why didn't they simply say "as soon as our engineering team became aware of the bug..."?
 
Being fired.

There's the famous story about some visitor to Apple being accosted by Jobs with a question "what have you done for Apple lately?" in an elevator and when the guy didn't have a good answer for him Jobs said "you're fired!" when the guy was just a visitor to Apple.

You figure he'd have a visitors badge and someone accompanying him but maybe things were more lax back in those days.
 
  • Like
Reactions: outskirtsofinfinity
There's the famous story about some visitor to Apple being accosted by Jobs with a question "what have you done for Apple lately?" in an elevator and when the guy didn't have a good answer for him Jobs said "you're fired!" when the guy was just a visitor to Apple.

You figure he'd have a visitors badge and someone accompanying him but maybe things were more lax back in those days.

I am not sure what moral I am supposed to learn from this anecdote, but I think that’s the problem when you elevate a visionary and everything he does.

Steve was a product visionary, but this didn’t mean that everything he did was okay. Emulate what he did well, yes, but also identify when he was simply being a jerk and not seek to copy those actions.
 
  • Like
Reactions: I7guy
There's the famous story about some visitor to Apple being accosted by Jobs with a question "what have you done for Apple lately?" in an elevator and when the guy didn't have a good answer for him Jobs said "you're fired!" when the guy was just a visitor to Apple.

You figure he'd have a visitors badge and someone accompanying him but maybe things were more lax back in those days.
I think we could safely say that is apocryphal. :)
 
Why is that explanation only ever rolled out for Apple bugs, I wonder?
It isn't.

If your perception is that Apple gets excuses, it's likely because their software is overall less bug prone in the eyes of users.

I literally get a "critical update" alert for my Windows machine twice/week, so it's gotten to the point I just ignore them.
 
It's impossible to uncover all bugs in any software release no matter what company is involved. That's why releases continue to happen any why beta releases take place. If the bugs aren't found during the betas, you can't blame these companies for releasing a version they feel is ready.

Beta testers, what the heck have you been doing?


Proves once again that public beta testing is useless. Those doing beta testing are only doing that so that they can have newest iOS before most other people.
 
Proves once again that public beta testing is useless. Those doing beta testing are only doing that so that they can have newest iOS before most other people.
It would be revealing to know how many public testers reported bugs that were then fixed.

But Apple's not going to tell us that.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.