really apple, all those millions of dollars and you can't fix a bug before release date?
Yep! Was just about to post this. I'm disappointed, but I depend on my watch. If I had updated and something major wasn't working, I imagine I'd be a lot more angry than I am now. Hopefully they'll get it fixed in a timely manner.i'm really, really disappointed... I've been waiting sooooo impatiently for OS2.... however I'm glad they found and pulled it cuz I'd be PISSED if they had screwed up my watch!
That's incredibly common. You're just not aware of how many products slip delivery because of finding bugs last-minute.That's just awkward.
Barely, if only because of the huge deal surrounding this particular update. A mild inconvenience, at the end of the day.This is embarrassing.
Hence why they're fixing this before releasing it.U mean like ios 8.1 ?. .. Erm.. Awkward....
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.
No, embarrassing would be to release it with a major bug. I guarantee you Apple know the software they release has bugs in it. It will never be perfect. They weigh up the pros and cons and decide then if it’s worth going with.Whats lame? They found a bug and they're going to fix it! That's how it's done.
Embarrassing would be to release a software with bugs and fix those months later.
I really give them thumbs up for actually fixing a problem instead of shipping garbage like many other software companies nowadays. Especially the gaming industry ships half-baked crap and make you even pay for it.
i wonder what the bug is
That's just awkward.
So it is "lame" that they first debug and then release?Really lame Apple. I hope this and any other bug is squished before its released otherwise it'll be really embarassing.
release this week still hopefully?!
I have watchOS2 and the first native app that I updated to (Waterminder) goes into an infinite loading loop or simply crashes. Waterminder says it's an authentication bug.
Well at least no one on MacRumors will have anything bad to say about this.
This is embarrassing.
I'll bet that's why. It would explain why it wasn't caught earlier too.I'm on the WatchOS 2 GM and iOS 9 GM. Battery life on both have been stellar, as has reliability. My iPhone 6 Plus is a little more sluggish, but I've had FAR fewer random reboots.
The ONLY bug I've noticed with regard to WatchOS 2 happened when The Weather Channel released their updated app with WatchOS 2 support and a complication. I was getting all kinds of "location not enabled" errors, even though my iPhone was set to allow the app to use my location always. Nothing worked. I had to disable location services for that app and then re-enable them to get it to work.
If the bug is going to cause all native watch apps to behave that way, I understand why they're delaying the release. It's not so much a performance issue with the watch itself, but how third-party native apps run.
Wouldn't say "sloppy" so much as their OSes are getting more complex and feature-packed. Add to the mix entirely new devices like the Watch and continuity vs. privacy isuues and concessions, and yeah... there will be a bump or two. Can be frustrating, for sure.
Complaining about software bugs - as if there should (or could) be absolutely NONE - is unrealistic... that's what many people are responding to.