Ah, I figured it might've been something like that. Thanks!macOS 13.4.1 is 22F82, except for the new M2 Macs released during WWDC, where 13.4.1 is 22F2083.
With the RSR installed, they are 22F770820b and 22F770830b respectively.
Ah, I figured it might've been something like that. Thanks!macOS 13.4.1 is 22F82, except for the new M2 Macs released during WWDC, where 13.4.1 is 22F2083.
With the RSR installed, they are 22F770820b and 22F770830b respectively.
It's much easier to downgrade rsr updates than point releases. This is especially so for iOS and iPadOS when they cease signing previous versions.I wonder why Apple don’t just call the version 16.5.1.1. We use that version number format in work all the time for emergency fixes.
effecting my solar website.So, if I don't use Facebook, Instagram, WhatsApp, or Zoom (at least recently for Zoom), should I worry?
No, it seems there is no quality control at Facebook anymore and their site breaks from a harmless change to the browser version number 🙃
At Zoom and Meta? Probably not in case they cannot write a valid user agent parser to accommodate such as simple structural change. This has nothing to do with Apple.
Hmmm yes, sure…. When you do a change you will test all possible sites how they parse your user agent 😀
"Apple" and "regulated convention" seldom go in the same sentence.This is why the important things are following a regulated convention and thus parsers are made based on these conventions specifications.
We don't know for certain why Apple pulled the update. I heard 13.3.1(a) had the same "problem" with the user-agent and it wasn't pulled...If Apple has to pull the update because it broke compatibility with commonly used sites and services, then it's absolutely on Apple to have tested this before deploying.
That would go against semantic versioning which pretty much every company would use.I wonder why Apple don’t just call the version 16.5.1.1. We use that version number format in work all the time for emergency fixes.
The user agent has the browser version number. All updates change the version number. This one happened to have a slightly weird version number that some websites didn't expect.Why did it need to change the user agent?
I mean the update only solved a bug...
If there was a problem with 13.3.1(a), I for sure didn't notice a thing. And I use Facebook on Safari every day. And I always install every update as soon as they arrive.We don't know for certain why Apple pulled the update. I heard 13.3.1(a) had the same "problem" with the user-agent and it wasn't pulled...
If you are using an app, rather than a browser, you won’t be sending a user agent string to the affected websites, so would not be affected.All my apps from Meta are working fine for me on my iPhone. Is this just affecting accessing those using safari?
Ah yes, the classic "you're holding it wrong" defense. If Apple has to pull the update because it broke compatibility with commonly used sites and services, then it's absolutely on Apple to have tested this before deploying.
Certainly I'd test all of the popular ones before deploying!
"... it broke certain apps such as Facebook, Instagram, Zoom.."
Now do Twitter!
on macOS I do have an alert on Facebook saying that my browser isn't compatible and show me a mobile version of it. Facebook were always picky when you try to change user agent so I'm not surprised for this issue. It can be fixed by changing the user agent for chrome, or simply just using...chome itself.Works fine for my iMac using Safari. Latest Safari, latest Ventura, and this latest RSR installed.... "works fine" meaning I just went to my Instagram page via Mac Safari browser. Everything is working fine.
Like my entire IG feed is full of Tiktok reposts. And dozens of BlendJet ads. So yeah, Instagram is working perfectly normal, exactly as Mark Zuckerberg intended. 🤷♀️