I guess you haven’t read the article thoroughly.I can see it on my phone but on my watch it’s not working. Here is what I see.
Anyone else ?
I deleted the app on watch and redownloaded it but no change.
I’d really like to know if this is happening to others before having to resetting my watch.
Actually I have read it … a few times;-)))I guess you haven’t read the article thoroughly.
The update enables oxygen monitoring on the iPhone not the Watch.
I am basing this off of previous years but both 13.7 and 14.7 came on the same day as that years main iOS release.Why did they release 15.7 RC then?
Seems like we are getting 18.6.2 for today. They probably where going to release it anyway today.At this point straight to 18.7 seems more likely. They already released 15.7 RC2 for Mac.
18.7 RC this week and then public release next week.
They finally didn’t, right?Seems like we are getting 18.6.2 for today. They probably where going to release it anyway today.
In a few minutes we’ll know.18.6.2 today ?
Please place your bets.
Probably just addressed a bug that was only affecting macOS. Not unheard of. 👍🏻Strange that we got RC4 for macOS 15.7 but nothing on iOS 18.7.
That’s when they use point updates for bug fixes. Usually it’s the macOS updates that are delayed with iOS updates coming out first and RCs are as far as I can remember are always released together. I definitely don’t remember a time when there were 4 RCs.Probably just addressed a bug that was only affecting macOS. Not unheard of. 👍🏻
If it was a pressing enough bug to address, then I think it would make sense to fix it in a new RC version rather than wait to release a fix for it in a point update. Maybe I’m wrong, but that’s what makes sense to me. 👍🏻That’s when they use point updates for bug fixes. Usually it’s the macOS updates that are delayed with iOS updates coming out first and RCs are as far as I can remember are always released together. I definitely don’t remember a time when there were 4 RCs.
It’s not about releasing another RC. It’s about there not being any for iOS despite there being 4 for macOS which is typically behind iOS in updates.If it was a pressing enough bug to address, then I think it would make sense to fix it in a new RC version rather than wait to release a fix for it in a point update. Maybe I’m wrong, but that’s what makes sense to me. 👍🏻
And like I said, maybe it was a bug that was only affecting macOS… 🤷♂️. I don’t know, I just don’t think it’s a big deal.It’s not about releasing another RC. It’s about there not being any for iOS despite there being 4 for macOS which is typically behind iOS in updates.