Apple Says Scanner Permission Error Fixed in macOS 11.6

Because maybe they just found out about it?

You're not making any sense... this was acknowledged that it was a bug by Apple prior to 11.6, they said it will be fixed in a future release, and then they released 11.6 with no release notes other then the standard 'bug fixes and general enhancements' boilerplate message they always use. Do you think it was just magically fixed in 11.6 and they don't QA their work and then were amazed when they randomly found out it was fixed?

This is why Apple should include actual release notes in updates. Not to find out weeks later through a support doc.

A lot of printers flat out don’t work on Arm Macs

And I've been a programmer for over 40 years.

I've only peripherally read this thread, but can say that scanners have always been a PITA with macs. I've always had HP scanners, and my history started with the hideously expensive flat bed scanner I owned. Eventually Apple/HP just stopped even trying to pretend they supported it. The next scanner I bought was a very beautiful standup scanner, all glass, and amazing, and it lasted a year or so, then another scanner, *POOP* stopped working with every update, and took either major gyrations or waiting for software support many times. Then I got an expensive 'all-in-one', and it had features dripping off of it, and most of them don't/won't work, and the same fun started with updates and it not working. Now, it works on mine, but refuses to scan on the wife's. (She actually thinks it works for me because it's afraid of what will happen to it if it fails. SCRAPPED)

I haven't had many printers fail to work after an update, but had a client that had to reload all their drivers, and I have had to reset the printer software system on a mac at least a few times back in the day.

So Apple has a problem with testing their updates. Apple has a problem with their contracted (most likely) programmers breaking things that worked previously. Apple is guilty of a lot of things, and attention to detail in testing 'their' software and updates is the biggest one in my mind. So permission errors in trying to scan makes me laugh. Apple appears to be unable to learn from their massive wake of screw ups in previous versions of macOS.

So how that makes me ignorant on 'how software development works' is kind of a reach, isn't it?

Apple *should* know when their software breaks things. Apple *should* know when previous fixes break from installing their updates. Apple *should* be doing a lot more testing than they obviously don't do.

I totally agree as I have to support all these bugs. Bugs like the printer/scanner issue mentioned take hours of trial and error to figure out as "sorry your printer or scanner won't work after I recommended you update to the latest OS" is not an appropriate answer.

Apple needs to slow down its release schedules for the major releases. Every year for a major release is a big ask and really isn't giving enough time to iron out issues fully.

Apple also needs to start focusing on issues that have been around for a while and not "just happened with the last update" -- it's common info that they'll ignore an issue that has been around for multiple Mac OS revisions. Take a look at Image Capture, Apple Mail, and other older apps that might have a new UI but still face the same irritating issues in every version.

Lol you have zero clue how software development works then.

And I've been a programmer for over 40 years.

I've only peripherally read this thread, but can say that scanners have always been a PITA with macs. I've always had HP scanners, and my history started with the hideously expensive flat bed scanner I owned. Eventually Apple/HP just stopped even trying to pretend they supported it. The next scanner I bought was a very beautiful standup scanner, all glass, and amazing, and it lasted a year or so, then another scanner, *POOP* stopped working with every update, and took either major gyrations or waiting for software support many times. Then I got an expensive 'all-in-one', and it had features dripping off of it, and most of them don't/won't work, and the same fun started with updates and it not working. Now, it works on mine, but refuses to scan on the wife's. (She actually thinks it works for me because it's afraid of what will happen to it if it fails. SCRAPPED)

I haven't had many printers fail to work after an update, but had a client that had to reload all their drivers, and I have had to reset the printer software system on a mac at least a few times back in the day.

So Apple has a problem with testing their updates. Apple has a problem with their contracted (most likely) programmers breaking things that worked previously. Apple is guilty of a lot of things, and attention to detail in testing 'their' software and updates is the biggest one in my mind. So permission errors in trying to scan makes me laugh. Apple appears to be unable to learn from their massive wake of screw ups in previous versions of macOS.

So how that makes me ignorant on 'how software development works' is kind of a reach, isn't it?

Apple *should* know when their software breaks things. Apple *should* know when previous fixes break from installing their updates. Apple *should* be doing a lot more testing than they obviously don't do.

Armageddon averted.