“watchOS 5.1.1 was pushed out [yesterday] following a spate of bricked Watches last week for some devices updating to watchOS 5.1,” Benjamin Mayo reports for 9to5Mac. “However, it looks like this update has also tipped the hat on a few upcoming goodies for Series 4 owners.”
“With iOS 12.1.1 and watchOS 5.1.1 installed, you can see seven new complications appear in the watch face gallery app for the Infograph and Infograph Modular faces: Home, Mail, Maps, Messages, News, Phone, and Remote,” Mayo reports. “These complications are selectable in the companion Watch app but unfortunately do not show up on the actual watch as functioning complications just yet; they render as blank zones.”
“The best theory as to why this has happened is that these complications were intended to be new features in the next Watch update, which should currently be in developer beta,” Mayo reports. “However, the bricking issue has caused Apple to rush out this version and seemingly forgot to strip out some of the unfinished features.”
Read more in the full article here.
MacDailyNews Take: Tim Cook’s sloppy Apple. Sigh.
Nearly every single time we’ve criticized Apple, it is due to lack of attention to detail. With Steve gone, it’s obvious that attention to detail has gone by the wayside in many areas. — MacDailyNews, October 31, 2018
Please. What other company can you name that gets after bugs as quickly as Apple does? Demanding constant perfection of anything or anyone is unrealistic.
Well, Apple is supposed to have teams that test for this stuff before release right?
So expect people to be harsh on them sometimes, just saying……
They’re exclusive to Series 4?
Another fine example of how miserable Pipeline’s Apple is.
Attention to quality? Nope.
Attention to user experience? Nope.
Well designed software, exuding elegance? Hell no.
It’s just embarrassing how miserable a leader Pipeline is.
A technologically harmless oversight with harmful PR implications.
I would imagine that fixing the bricking was super urgent, and the time involved to modify or remove the complications code was left in simply to speed out a resolution for customers with bricked Watches. The incomplete new complications is certainly not a big deal. If anything, it’s nice peek at some upcoming improvements.
Don’t care, if they don’t do anything and the only person to actually find it is this guy. They’ll work when 5.2 comes out probably in a couple weeks now. Way too much emphasis is placed on things that are a big yawner , now if something was actually broke, and the watch crashed… that’s different.
I don’t believe there is anything sloppy here. Getting the fix out quickly was of paramount concern and no harm is done by leaving in the complications code. Stability of the fix was very important and if you start messing with other code the chance for problems increases and the testing schedule gets longer.