Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
This bug was well known, as well as the other security bug Apple still needs to address. The security in iOS is a shambles every iOS breaks some form of security in iOS and Apple response silence until someone makes it public knowledge

Shambles is such an over exaggeration. It's a bug and small one that affected no one adversely.
[doublepost=1548956752][/doublepost]
I get what you're saying, and mostly agree. But given what I've seen in macOS and iOS as of late, I would not say Apple engineers are at the top.
[doublepost=1548954937][/doublepost]

Reports seem to suggest it was reported a week prior. It would seem a breakdown in processes contributed to the delayed reaction. That breakdown is still on Apple though.

Nobody has any idea how many junk bug reports they work through daily. Some repeatable and some not easily repeated. I would say ones from developers and security researchers get the highest priority than ones reported by housewives. Someone has to sort through the garbage to get to the true bug reports. What we also don't know is if the ability to shut off Group FaceTime existed and was functional the day it was reported + any lag time in seeing it. Not acknowledging something before a fix or partial fix can be put in place is better than accepting it as a bug and broadcasting it. Apple knows that even if you broadcast to every user to turn off Group FaceTime most would ignore it.

I'll add that I am suspect the child actually found it and am suspicious of the mother who has retained a lawyer. Seems like someone might have pumped them with the info or they are looking for a payout.
 
Nobody has any idea how many junk bug reports they work through daily. Some repeatable and some not easily repeated. I would say ones from developers and security researchers get the highest priority than ones reported by housewives. Someone has to sort through the garbage to get to the true bug reports.

For sure. But ownership still lands solely in Apple's lap. One week is a long time for a serious bug to go unchecked. If Apple can't sift through the crap in a reasonable time, they should hire more people to do the work.
 
  • Like
Reactions: Marekul
Hmmm so it “seems” where there is smoke there is fire for Qualcomm when they are investigated. But it “seems” where there is smoke there is fire to not be the case when Apple is investigated....Gotcha...it's clearer now :)
We will find out if this is legitimate or grandstanding by New York State.
 
Last edited:
As a New Yorker, may I ask Apple to go away then? :p

Not about the bug, but Apple’s delay in their response to it.

It was reported that it was sent to them a week ago. For a company the size of Apple that deals with as much as they do.. that's not too long.
 
It was reported that it was sent to them a week ago. For a company the size of Apple that deals with as much as they do.. that's not too long.

No tit for tat with you, but when a huge corporation touts privacy and something like this happens (it hasn’t been the first time in the last 18 months either - the security log in errors in Hugh Sierra etc.), I fully understand why some folks would take action.

For me, it’s just another disappointing glitch in Apple’s software lately.
 
Oh, well that makes it alright then...
If you lip reader it’s ok otherwise you just get to see the faces not hear the secret conversations. Don’t put words in my mouth, never said it was “all right then”.

Simply pointing out that it wasn’t an addative invasion of privacy.
 
If you lip reader it’s ok otherwise you just get to see the faces not hear the secret conversations. Don’t put words in my mouth, never said it was “all right then”.

Simply pointing out that it wasn’t an addative invasion of privacy.

*for you.

For most people, it absolutely would be.
 
  • Like
Reactions: Marekul
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.