Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
I was thinking. If the build of Apple watch yesterday is the same as the final build, we could see iOS and macOS finals this week. I need to check the build number of the watch.
 
I was thinking. If the build of Apple watch yesterday is the same as the final build, we could see iOS and macOS finals this week. I need to check the build number of the watch.

watchOS 3.2.3 beta 4 build #16G71a

Seems like all the 10.x.x final releases as of late have been on Monday's though.
 
watchOS 3.2.3 beta 4 build #16G71a

Seems like all the 10.x.x final releases as of late have been on Monday's though.
Thats a strong indication of a final build. It no longer has the "5". Revision letter is okay as it sometimes makes it into the final build, but the big tell is no "5".
 
  • Like
Reactions: PR1985
I think the fact that they stopped signing is a good indication that 10.3.3 is almost ready. Would not be surprised to see a release today
 
  • Like
Reactions: PR1985
I don't read much into the not signing of 10.3.1 anymore. It's actually been a really long time since iOS 10.3.2 came out. They usually stop signing the the older version within a week or two. Not over a month.

With the release of the watchOS beta this week I still see a very small possibilty we get 10.3.3 final this week. Next Wednesday seems like it will be the day for iOS 11 Beta 3 and iOS 10.3.3 final.
 
I don't read much into the not signing of 10.3.1 anymore. It's actually been a really long time since iOS 10.3.2 came out. They usually stop signing the the older version within a week or two. Not over a month.

With the release of the watchOS beta this week I still see a very small possibilty we get 10.3.3 final this week. Next Wednesday seems like it will be the day for iOS 11 Beta 3 and iOS 10.3.3 final.
Apple told some users that they wait, because they are aware of the fact that there is something wrong with iOS 10.3.2.
 
Apple told some users that they wait, because they are aware of the fact that there is something wrong with iOS 10.3.2.
Hmmm. I haven't heard of that, any sources? Not that I don't believe you, I'm just interested.

It still doesn't change the fact that we got a watch beta this week. The only way we are getting 10.3.3 final this week is if the that watch build is a final. But why would they release it to dev only 2 days before public. Thats weird.
 
Hmmm. I haven't heard of that, any sources? Not that I don't believe you, I'm just interested.

It still doesn't change the fact that we got a watch beta this week. The only way we are getting 10.3.3 final this week is if the that watch build is a final. But why would they release it to dev only 2 days before public. Thats weird.
Good question. I know, that I read it somewhere. It is possible that it was on MR forum.
 
Good question. I know, that I read it somewhere. It is possible that it was on MR forum.
I feel like if there were that many problems with 10.3.2, they would've pushed 10.3.3 out faster and made a 10.3.4 beta for all the changes that they have been testing in 10.3.3. Because Apple does not tell the average consumer how to downgrade and they would never recommend that via AppleCare or Genius Bar.

Its only now in iOS 11 that they have provided a step by step tutorial for downgrading. 3 years after the initial release of the public beta. But the average user has no idea about the public beta anyway.
 
I feel like if there were that many problems with 10.3.2, they would've pushed 10.3.3 out faster and made a 10.3.4 beta for all the changes that they have been testing in 10.3.3. Because Apple does not tell the average consumer how to downgrade and they would never recommend that via AppleCare or Genius Bar.

Its only now in iOS 11 that they have provided a step by step tutorial for downgrading. 3 years after the initial release of the public beta. But the average user has no idea about the public beta anyway.
The main reason was battery drain, if I recall it right. But as I posted here things don´t work perfect. Not on my phone and a little bug on my iPad4.
The iPad 4 bug started with 10.3. Settings and there my iCloud Profile photo doesn´t show up until I tap on the "photo symbol" to open up Account and iCloud Settings.
 
The main reason was battery drain, if I recall it right. But as I posted here things don´t work perfect. Not on my phone and a little bug on my iPad4.
The iPad 4 bug started with 10.3. Settings and there my iCloud Profile photo doesn´t show up until I tap on the "photo symbol" to open up Account and iCloud Settings.
I find it so weird that there could be that big of issues with 10.3.2. It such a small update form 10.3.1.
 
10.3.2 has been fine for me except for the setting time zone bug that was introduced in 10.3. But it has been reportedly fixed in 10.3.3 and I can't wait to fix that annoying bug with the install!
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.