Sidebar Sidebar
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.

What was the bug?

How could they not have found this show stopper? Apple is getting careless with their QC.
 
Yep, James Thomson seems to be the one who identified the issue - check his tweets at https://twitter.com/jamesthomson for more information.

Basically it appears to be a FairPlay/encryption bug that causes watchOS 2.0 apps to crash on launch. Basically it's much like what happened last year with HealthKit apps at the launch of iOS 8.
 
friednoodles said:
Yep, James Thomson seems to be the one who identified the issue - check his tweets at https://twitter.com/jamesthomson for more information.

Basically it appears to be a FairPlay/encryption bug that causes watchOS 2.0 apps to crash on launch. Basically it's much like what happened last year with HealthKit apps at the launch of iOS 8.
Click to expand...
Yep - saw that and believe that is it - though the one I installed doesn't crash and looks very nice. The complication is somewhat boring though. :)

I am more surprised about all the posts by people whining that 2.0 was not coming out today. Finding a bug happens and it is always best to find in advance - no matter how many beta versions were tested or released. The OCD of many cannot tolerate anything outside their norm. :)
 
  • Like
Reactions: RabbitLuvr
friednoodles said:
Yep, James Thomson seems to be the one who identified the issue - check his tweets at https://twitter.com/jamesthomson for more information.

Basically it appears to be a FairPlay/encryption bug that causes watchOS 2.0 apps to crash on launch. Basically it's much like what happened last year with HealthKit apps at the launch of iOS 8.
Click to expand...

I'm old enough that when I see "HealthKit" the first thing I think is "HeathKit."
 
  • Like
Reactions: jamespa66 and Denmac1
I too was looking forward to the new watch iOS but I am fine with waiting until they have it right. Will ,air the experience even better.
 
Whatever the bug it must have also stopped the release of OS2 apps. Running the watch GM update I was waiting for a long list of app updates yesterday but they never came.

Running OS2 update for a week now - no issues, battery is fine, about 30% remaining late into the night - same as before.
 
  • Like
Reactions: cwosigns
I think some of the frustration is we've not had many updates to the watch, I.e. One and this is such a performance enhancement it should be like getting a brand new watch. We're all just super keen to have this new watch...
 
  • Like
Reactions: jjm3
prycop said:
Whatever the bug it must have also stopped the release of OS2 apps. Running the watch GM update I was waiting for a long list of app updates yesterday but they never came.

Running OS2 update for a week now - no issues, battery is fine, about 30% remaining late into the night - same as before.
Click to expand...

Same here. I only have one WatchOS 2 app on my watch, and that's The Weather Channel. That app also failed to start on launch, requiring toggling some things off/on in the Watch app on the phone to get it to work.
 
cwosigns said:
Same here. I only have one WatchOS 2 app on my watch, and that's The Weather Channel. That app also failed to start on launch, requiring toggling some things off/on in the Watch app on the phone to get it to work.
Click to expand...
I have two apps running native now and as complications but they are pretty boring but wanted to try. On my watch, the battery has been insanely good with GM. Since I wear my watch to bed to track sleep and silent alarm, I would normally wake up with 92-93% battery from a full charge. Now, with GM after 7 hours of sleep it is 95%. I finish the day with 50-60% battery with at least one hour workout and all rings met. That is with starting the day at 10pm. I charge from 8-9ish each night.
 
cwosigns said:
I hope my Watch is able to update once the final version is released.
Click to expand...

In doing a little research on the developer forums, I stumbled across this which should give those of us running the GM some peace of mind.

The build number of watchOS 2.0 GM is 13S343. You will only be offered an update if the build number of the final release is higher than this. The 13S won't change but, if the build is improved on before final release, then the 343 will be incremented and this will trigger an "Available Update" via the Watch App. If not, there won't be a way to update past the GM because it will be identical to the final release version.



Since this is the first major upgrade in watchOS, there are a few unknowns and so if you want to do everything possible clear potential obstacles to a smooth transition for both watch and phone then you could follow these steps:

  1. Delete all beta Profiles (Watch & Phone)
  2. Unpair the Watch
  3. Setup the iPhone as a new Device with the final Release Version of iOS 9.0 with iTunes
  4. Re-Pair the Watch as a new Device


Again, not all of these steps should be necessary but, taken together, they remove potential issues.



-Max
​
 
I'm starting to wonder if the bug was iOS 9 was sucking the battery out of the Watch 50 times faster? Only a guess obviously, but I am seeing a lot of people having huge battery drain today using the new OS and Watch OS2 GM, and some current OS 1.0.1.

I was off today, did a lot of outside yard, house work and didn't wear the watch at all so I can't confirm it. I'll wear it tomorrow though and see what happens.
 
bmac4 said:
This is the update I was looking forward too. Sure iOS 9 is cool, but the watchOS was a huge improvement. I can't believe after all that beta testing we they still had a bug big enough to stop the release. Can't say I am not disappointed.
Click to expand...
Same! When I saw the news it was delayed yesterday...ugh, it was deflating!
Just hope they get it fixed within a week or two.
 
You must log in or register to reply here.
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.
Top Bottom
Back