This FaceTime bug is bad. Really bad. Especially for a company that is pitching itself as the most privacy-centric in the industry. You know what’s worse? Coming out and saying that you’ll have a fix “later in the week.” Yikes! Way, way too long.
Jonathan's location at time of posting:
Fairmontstationary-3.6 km/h39%
Comments (13)
Dark Sky
via
cleverdevil.io
Weather at time/location of posting — Mostly Cloudy with a temperature of 73.78°F and 50% humidity.
VM (Vicky) Brasseur
via
Twitter
A new iOS beta came out today, probably because of this.
So it’s not like they’re not on it.
Jonathan LaCour
via
Twitter
I suppose? I am glad they’re aware and working on it, but this type of bug is an all-hands-on-deck, shits on fire emergency. Push notify users to temporarily disable FT. Find a server side workaround. Try and get a fix out within 24-36 hours.
VM (Vicky) Brasseur
via
Twitter
It’s definitely bad, don’t get me wrong. It should never have been released. They are undoubtedly learning many lessons from this one.
Jonathan LaCour
via
Twitter
Indeed. I have immense respect for Apple, and I expect better from them. These things happen, just a bit disappointed in the response.
VM (Vicky) Brasseur
via
Twitter
Cosigned. To quote something I said in an IRC channel earlier: “But generally it's a big screw up by Apple and pretty disappointing.”
It’s surprising how long it took to turn up in the wild, though. Makes me wonder whether it’s a trickier bug than we think.
Jonathan LaCour
via
Twitter
Almost all bugs are trickier than we think 😉
simonwoods
via
Micro.blog
@cleverdevil this app was the main event at WWDC. Tim Cook was in the demo. Just terrible.
cleverdevil
via
Micro.blog
@simonwoods brutal. I understand that bugs happen, even with a ton of QA, but the blasé response is baffling. If I were Apple, I’d send a push notification to all FaceTime users with a link to a kbase article covering the bug and instructions on how to temporarily disable FaceTime.
amit
via
Micro.blog
@cleverdevil @simonwoods Only way they are getting a pass on this is if they release a fix within a day and push it to all affected devices. If not, they better just force users to disable it or disable the affected feature somehow on server side. This is terrible.
amit
via
Micro.blog
@cleverdevil @simonwoods and of course they have already done the later. Phew!
Rich Ellis
via
Twitter
@iMore story was updated to say that Apple has taken FaceTime group call down until the fix is out: apple.com/support/system…
Agreed, though, this should have been part of their initial response
simonwoods
via
Micro.blog
@amit @cleverdevil One of the problems with Apple's growth is that more people than ever are aware of just how much money they have, and then make the over-simplified assumption this means there should be no problems. However, much of their apparent neglect of the Mac and bafflingly bad PR are more than avoidable so I still think they could be doing much better.
Comments (13)
Weather at time/location of posting — Mostly Cloudy with a temperature of 73.78°F and 50% humidity.
A new iOS beta came out today, probably because of this.
So it’s not like they’re not on it.
I suppose? I am glad they’re aware and working on it, but this type of bug is an all-hands-on-deck, shits on fire emergency. Push notify users to temporarily disable FT. Find a server side workaround. Try and get a fix out within 24-36 hours.
It’s definitely bad, don’t get me wrong. It should never have been released. They are undoubtedly learning many lessons from this one.
Indeed. I have immense respect for Apple, and I expect better from them. These things happen, just a bit disappointed in the response.
Cosigned. To quote something I said in an IRC channel earlier: “But generally it's a big screw up by Apple and pretty disappointing.”
It’s surprising how long it took to turn up in the wild, though. Makes me wonder whether it’s a trickier bug than we think.
Almost all bugs are trickier than we think 😉
@cleverdevil this app was the main event at WWDC. Tim Cook was in the demo. Just terrible.
@simonwoods brutal. I understand that bugs happen, even with a ton of QA, but the blasé response is baffling. If I were Apple, I’d send a push notification to all FaceTime users with a link to a kbase article covering the bug and instructions on how to temporarily disable FaceTime.
@cleverdevil @simonwoods Only way they are getting a pass on this is if they release a fix within a day and push it to all affected devices. If not, they better just force users to disable it or disable the affected feature somehow on server side. This is terrible.
@cleverdevil @simonwoods and of course they have already done the later. Phew!
@iMore story was updated to say that Apple has taken FaceTime group call down until the fix is out: apple.com/support/system…
Agreed, though, this should have been part of their initial response
@amit @cleverdevil One of the problems with Apple's growth is that more people than ever are aware of just how much money they have, and then make the over-simplified assumption this means there should be no problems. However, much of their apparent neglect of the Mac and bafflingly bad PR are more than avoidable so I still think they could be doing much better.