Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Really curious what the bug is...

I've been running the 2.0 GM since this weekend and it's been fine. It's been said that there is an issue running 2.0 apps (something to do with FairPlay DRM) but an app I use (WaterMinder) was updated this morning with a 2.0 compatible app and it seems to be working flawlessly. Haven't actually ran into any bugs at all yet.
 
i wonder if this will be released out of the typical 10:00 am PST

released when its ready then.. could be early in the day, or later in the day on any given day.
 
No, it does not. Companies that develop software classify bugs according to severity level. A top severity bug could be one that disables or seriously compromises a significant feature without reasonable workaround. It does not have to be a security problem. Bugs in the top severity level would automatically delay release.

Apple has never delayed a launch. So this has to be significant.
 
That makes it a few less days that I have to go without watchOS 2, as I'm not updating my iPhone 6 to iOS 9 until I get the 6S Plus.
 
Maybe I missed it but does watch OS2 make apps open a lot faster? Cuz trying the watch at the store and noticing how long it took to open the weather made me not buy the watch.
 
  • Like
Reactions: studio¹³¹
There is a first time for everything...I wonder who's getting fired for this...Or getting a promotion for catching the bug before the release
 
Perhaps that explains some of the people on the forums who have said that the new native apps being updated for Watch OS 2 today have been crashing repeatedly on their GM build.
I've been using the Weather Channel native app on the watch and it's running fine.....
 
Ah well, I like that they are holding it back due to a recently discovered bug.
Why push it out before it is ready?
Chances are it is the battery-draining thing that so many have experienced on the GM?
It happened on my wifes sport, but not on mine.
An unpair and re-pairing solved it for her, as it did for many others though.
But imagine all the calls and genius bar work this would have created if released to the general public...
that's what I'm thinking too... this was all over reddit, the battery issue with the pairing/updates.
 
problem with this is there will always be bugs and the software then would never be released.
But this apparently was a significant bug, akin to iOS 8.0.1. That one got resolved in a day. Hopefully this is the same.
 
Well I'm pissed off, I guess it's better they're admitting there's an issue now though before screwing up a release. May as well just go to the GM I guess now.

Why would you install the GM knowing there is a major bug in it? People who got the GM will have to update to this new one also.
 
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.

Thats not a bug.. thats the way its supposed to be. You aren't supposed to be able to play the music on the watch speaker, only headphones.
 
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.

If that is true for everyone... There is going to be a lot of ticked off watch owners.

You don't pony up the kind of scratch Apple is asking for those then render them nearly useless with an iPhone update... or rather you shouldn't get away with a move like that... oh yeah, this is Apple... they will get away with it... and be praised for it.

I am running iOS 9.1 with watchOS 1.1. I have no issues.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.