Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Hahaha this is how it panned out in my head as I read that:
Employee in charge of mass-distributing the update hovers their finger above the "launch" button, when suddenly an engineer bursts through the door and yells, "Wait! The San Francisco font isn't rendering on one of the new watch faces! Instead it's...Time New Roman!" The engineer then passes out from shock as the employee in charge of distribution of WatchOS 2 just looks out the window pondering how life could let him down like this.
 
I have been running the OS 2 GM, and the only bug I have noticed is that the synced music will not play on the watch's speaker. It still asks to pair with iPhone or Bluetooth speaker. Other than that, it has been golden. I have it running along with iOS 9.1 PB.
 
I was running the GM release and it was KILLING my battery. It was going down 1.5% every 3 minutes. My watch wasn't making it to 4 hours before turning off.

I'm glad they are delaying if this is the bug.
 
Well this is good news considering if there was a bug significant enough to cause daily issues, theres no way to downgrade the watch without sending it out to Apples Depot repair.
 
Like others have said it must be a major bug to delay a worldwide release as all software has bugs. I'm with everyone here though. Kid in me wanted it now (the official not the GM) while the rational me is willing to wait in order to release the best product possible.

It does make me wonder about the GM version though. Anyone know what the bug is and if it exist in the GM?
 
So a programmer just found this bug today when they are going to release? Sounds like a crappy programmer

This is why we need a "thumbs down". How silly. You've obviously never programmed anything in your life and know nothing about programming. Apple did a good job finding this before release and you're condemning them.
 
  • Like
Reactions: Enygmatic
9.1 fixed that issue. In any event, I'm disappoint. But I guess I can wait.
So, I have been on several versions of the 9.0 beta and the 9.1 over a week and have never had any problem with watch notifications. Is it just some specific apps, or all notifications?

can anyone else corroborate this seemingly unfounded rumor or statement from the above poster?
 
Comments section full of people who make 3-4 grammatical and/or spelling errors per post, whining about how 'easy' programming an entire operating system should be...

...adorable.

Take your time, Apple; get it right. GM 2.0 is running well for me, but a bunch of bricked Watches would piss everyone off (justifiably, since they'd all have to be sent in).
 
Well done Apple.

I know you NEVER release any software that you know has any bugs in it.
 
  • Like
Reactions: navaira
Well if I was a watch owner I'd be pleased they were not giving me something with a serious bug. Sure everyone wants it as soon as possible but at least they had the balls to hold it off. I'm sure some others would not have.
 
  • Like
Reactions: Enygmatic
Think of the positives. Your iPad gets updated today, and your watch gets updated another day. 2 days of fun!

accept for we dont know when the watch will be updated because of this bug. it could be tomorrow, it could be a week later.
 
Well at least no one on MacRumors will have anything bad to say about this.
Are you serious? This will be a major opportunity for the nay sayers and Apple haters to go absolutely wild. And a good opportunity for me to populate my ignore file.
 
So a programmer just found this bug today when they are going to release? Sounds like a crappy programmer

You don't realize the complexity of an OS software release. There are hundreds of developers working on the os. There are 1000s of bugs all the time (obviously most of them are not showstopper bugs and are deferred to later releases). There is most certainly round the clock testing going on done by testing teams around the world. Fixed bugs can cause regressions that need to be found. Even with only critical bugs getting fixed and make it into the release code line (and I am sure they will be code reviewed and need high up approval so close to release time), and even with full testing there are always holes in your test plans. Things can slip through. Also timelines are extremely tight. Yes in an ideal world they would have months too harden a GM release, but in reality it's just a couple of weeks.. So things can slip out. It's all about risk management and improve testing for the next round.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.