Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Disappointing for sure, as I was looking forward to the new watch faces, but I would rather, like many others, have a version working as best as possible with as few bugs as possible (if any at all) than one that would potentially render a device useless.
 
  • Like
Reactions: nrose101
"but the company will need to make some final tweaks to address the discovered bug before it feels comfortable releasing the updated operating system to the public."

So, this is a new policy for Apple?
 
Really? I'm glad I read that before the 9.0 update came out. I can see a lot of annoyed people tomorrow if that's the case.
I am running the public beta on my phone and watchos 1.0.1 and it works just fine. But I do not know what will happen when the full release comes out
 
  • Like
Reactions: fearcake
I guess the question now is should one update their iPhone or wait till it is ready to avoid watch/phone compatibility issues
 
Really lame Apple. I hope this and any other bug is squished before its released otherwise it'll be really embarassing.
All major software is released with known bugs. The question is when to draw the line. When is something good enough for release? Checking software with open bug trackers, you'll see that for example each release of Google Chrome comes with hundreds of known bugs as well as when they deem they should be fixed, depending on severity. It's common to know a bug and schedule it for fixing only by the next two releases or so. Simply because dev teams have their hands full of more important stuff.
 
38mm black sport owner here. Whilst I'm a teensy disappointed I won't be getting watchOS2 today, I'd far rather have it when it's ready vs now when it's not. Heavy user of Apple Pay for the morning coffee so if there's any possibility of the bug affecting security, especially of Apple Pay, then by all means fix it then release - not vice versa.
 
Maybe it was something with the provisioning , but at any rate no biggie, I released a package today, that I was supposed to release yesterday (and the whole Federal government didn't shut down :D)

To be honest, I was probably going to wait anyway, and do W/OS2 and iOS9 on the 25th ... via a new iPhone 6S+ :)
 
This sucks. iOS 9 is incompatible with watch OS 1.0.1. I get no notifications

Whoa if this is true then to me the watch is already broken.

I love how people are so complacent here. They give Apple cheers but if their own IT at their company told them "we can't give you your new computer today because we screwed up" they'd probably call their IT idiots.
 
It takes guts to say there is something wrong with our product. Kudos to Apple for acknowledging this and letting us know that we are working on a fix.
Like any last minute bugs discovered, I'm sure this has been assigned critical priority, an internal timeline has been drawn to monitor progress and the apple developers are working hard to get a fix out.
 
Well, at least now I'll remember to pack my charger. Just found out that you have to have your AW plugged in to upgrade it—even if the battery is fully charged. I was really looking forward to this today. Probably even more than iOS 9 because I've been playing with the beta on my iPad Air 2 all summer.

Same boat here.
 
Clearly Apple doesn't care about the Watch as a key product line. At wwdc they glossed over the watch, and didn't really highlight anything for it. And now it shows they aren't really devoting resources to it, having been through multiple betas.

I'm starting to regret my purchase of this expensive watch that only shows notifications
 
  • Like
Reactions: studio¹³¹
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.