You missed the cheeky wink emoji at the end dude.. LolWell done Apple.
I know you NEVER release any software that you know has any bugs in it.
You missed the cheeky wink emoji at the end dude.. LolWell done Apple.
I know you NEVER release any software that you know has any bugs in it.
Because production is always a linear progression...That's very unlike Apple, even after months of beta testing!?
Is Apple OS getting sloppy?
There's an "ignore list"? I did not know you could do that but I am certainly going to take advantage of the function in the future. Thanks.
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.
No.
Only a few people own Apple Watches and millions own iPhones.
Sounds like an all nighter at the very least..Let's just say a lib command runs into a php stack fault causing a default memory flatulence.
What would you do with that information?
I've been using the Weather Channel native app on the watch and it's running fine.....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.
Well I have the GM installed![]()
that's what I'm thinking too... this was all over reddit, the battery issue with the pairing/updates.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...
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.problem with this is there will always be bugs and the software then would never be released.
Wonder if it'll be released as 2.0 or 2.1. I'm running the 2.0 GM
I'm shocked... shocked that someone commenting on this thread has a clue about how software development actually works.
Really lame Apple. I hope this and any other bug is squished before its released otherwise it'll be really embarassing.
2.0.1 is my guess.![]()
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.
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.
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.