I don’t have elaborate HomeKit setups (I have two homes with HK), but everything is working perfectly for me on the “legacy” architecture so I have absolutely zero plans myself to update until either this has been around for a while, or I have no other choice but to update.
I’d say the first thing to try if you are seeing excessive watch battery drain post-update is to power cycle both the phone and the watch and see if that makes things better.
I just installed 9.4 a couple of hours ago on my Ultra. It’s probably too soon to say, but I’ve not noticed any increased battery drain compared to 9.3 and earlier so far.
I’m not sure what you’re talking about here. I use Quick Look all the time and haven’t seen any problems with image display order.
Yeah, as @ddmiller wrote, it’s something to look at now that Apple has brought the new Home architecture back. I’m a little worried about it because I have a LOT of devices and scenes and automation and I would be very unhappy if I lost them.
Someone sees this with the Apple Watch or iPhone or iPad after every update. Let it finish setup and indexing and all the necessary background cleanup tasks for a day or so, and then see if the battery life is still being negatively impacted.
I mocked Apple leading the release notes with the new emoji not because I think it’s silly to add them (well, sort of) but mostly because I think it’s ridiculous to promote the addition as the top improvement. I have to assume that adding a new emoji is trivially easy and isn’t done by a senior-level engineer. As David Shayer wrote, it’s highly unlikely that bugs will be fixed this late in the release cycle because the risk of causing other problems is too high.
Voice Isolation for regular calls is NOT on by default. I too had a hard time figuring out how to enable it. You have to access it from the control center WHILE A VOICE CALL IS ACTIVE — otherwise the setting is not visible. Setting it once appears to leave it at that setting for future calls though.
This is completely obscure on Apple’s part imo — why this setting isn’t available under Settings → Phone is beyond me.
Well, after more than 40 years in Tech, I know how much work goes into writing a good bug report. I frankly have little confidence at this point that Apple really cares much about user-reported issues, and that’s why I’m not willing to put the hard work into trying to nail down a well-written bug report that just gets sucked into the black hole at the center of Apple Park…
Sure, but I was sharing that article for his point about when in the cycle bugs are likely to be fixed.
I’m no fan of reporting bugs to Apple either, but if no one does it, we can’t necessarily expect them to be noticed and fixed.
In September 2021, I reported a bug to Apple about how Audio MIDI Setup still used the term “master,” despite Apple having officially deprecated the term. (Gotta walk the walk, Apple.) Apple finally fixed it in Ventura, a year later, but still hasn’t corrected a screenshot in the app’s help. I’ve sort of enjoyed repeatedly plinking them about it.
I guess you could argue that should actually be the job of the beta testers and devs. Now obviously, the more that report bugs, the better the odds of getting them fixed should be, and yet there’s indeed considerable doubt as to if more user reports actually lead to fewer bugs. I find this a very interesting issue, and I’m entirely unsure which side I come down on personally. I think we’re quite susceptible here to believing what we would want to be true though.
On at least some of the bugs we’ve discussed here on recent releases, there’s also been a lot of discussion on Apple’s own developer forum. That’s where I’d expect Apple to (a) find a common problem, (b) solicit help if they can’t reproduce it from the material already there, and most importantly (c) provide -some sort of feedback-.
The first thing I noticed was that my iPhone wasn’t able to connect to my smart thermostat. I had to “reconnect” everything this morning, but that didn’t help last night when I had to get out of bed and reset my thermostat to sleep mode.
A couple of other oddities…at least with iOS and iPadOS so far…it forced me to re-authenticate both my primary and our secondary AppleIDs and typically it’s either only the master one or not at all. And it turned auto download and auto update back on which I had deliberately set to off and don’t download to control both bandwidth usage if I’m out of the house and one should never just turn auto update on IMO as Apple has pulled an update more than once. And on iOS and iPadOS it forced me to reconnect all my cards to Wallet although it remembered the previous cards and all I needed to do for the non Apple Card one was put in the CVV.
Any indication that 16.4 has done something to improve the crappy performance of Weather’s precipitation map? It’s raining cats and dogs again today, yet my vicinity is completely blanked out in Weather’s rain map. I can see the rain 300 miles away though.
I installed the update to Ventura 13.3 yesterday. I have an M2 Mac Mini with a 3330x1440 main monitor, and I am also using a ViewSonic 14" display I normally use with my laptop. Today I noticed that the Aerial Screen Saver was only showing on the small monitor. The big monitor has a blank screen.
I also tried Electric Sheep, which I haven’t used in a couple of years, but it has the same problem. I tried reinstalling the screen saver and other troubleshooting with no luck. I asked about this on the Aerial discord server, and I see a number of other people with the same issue (including people with only one monitor). The Aerial Devs have been responsive in the past so maybe I’ll get more info. Wondering if anyone else is able to confirm this is a macOS issue, or what else might be going on?
I’m having the exact same problem; two monitors and Aerial only runs on one. I reset the PRAM and Aerial was back to normal but only the first time it ran. Then it quit working again.
It may be more than third-party screen savers. My photo based slide show using the built-in screen saver will only display on one screen with the update to 13.3. The non-photo based built-in screen savers work on both screens.
I have a MacStudio with two 27" 4k monitors coming off it.
An unusual thing happened after doing the 13.3 update this morning. Finder doesn’t want to let me change the app to open .pkg files, and it doesn’t show Pacifist or Suspicious Package as options when secondary clicking the file (although I can still do it through the “Other” option). Even when using the “Other” option, it does not allow me to set another app to “Use this application to open all documents like this one.”. I verified this with a couple of my test machines, fine before 13.3, grayed out after. I can see where this might be a security change, I guess.
The Duplicates album now detects duplicate photos and videos in an iCloud Shared Photo Library.
Just to be clear, prior to iOS 16.4, it wasn’t just that duplicate detection was not available in the shared library…. It was that duplicate detection was disabled completely — even in your personal library — if you enabled the shared option.
I can see the rain 300 miles away though.