SFAuthorizationPluginView and MacOS Tahoe

Testing my security agent plugin on Tahoe and find that when unlocking the screen, I now get an extra window that pops up over the SFAuthorizationPluginView that says "macOS You must enter a password to unlock the screen" with a Cancel (enabled) and OK button (disabled). See the attached photo. This is new with Tahoe. When unlocking the screen, I see the standard username and password entry view and I enter my password and click OK. That is when this new view appears. I can only click cancel so there is no way to complete authenticating.

As of today, My Mac is up to date with macOS Tahoe Beta 26. My plugin is added to system.login.screensaver.

It appears that Tahoe handles multiple mechanisms that display UI differently that previous OS versions.

It appears that Tahoe handles multiple mechanisms that display UI differently that previous OS versions.

Can you elaborate on that? Are these both your mechanisms?

Share and Enjoy

Quinn “The Eskimo!” @ Developer Technical Support @ Apple
let myEmail = "eskimo" + "1" + "@" + "apple.com"

I have resolved my issue, but I want to confirm that if multiple mechanisms use SFAuthorizationPluginView then multiple views will appear when unlocking the screen.

I have resolved my issue

Cool.

but I want to confirm that if multiple mechanisms use SFAuthorizationPluginView then multiple views will appear when unlocking the screen.

Again, I need clarification here. I’m not even sure if that’s a question or a statement of your goals )-:

Share and Enjoy

Quinn “The Eskimo!” @ Developer Technical Support @ Apple
let myEmail = "eskimo" + "1" + "@" + "apple.com"

This is a statement about how SFAuthorizationPluginView works with multiple mechanisms: The first mechanism displays its view and later sets its result. The view continues to display. Then the other mechanism displays its view over the top of the first view. (The first mechanism was not developed by me.)

Question: How can a mechanism take down its own view? Is this supposed to happen automatically after the mechanism sets its result?

Thanks for the clarification.

So this is a regression in macOS 26 beta, right? That is, the same setup works as expected on macOS 15?

Share and Enjoy

Quinn “The Eskimo!” @ Developer Technical Support @ Apple
let myEmail = "eskimo" + "1" + "@" + "apple.com"

I think this is just how macOS 15 and 26 work. I hadn't noticed it in the past because my view completely covered the earlier view on macOS 15. It doesn't quite cover it on os 26. Not a bug. The earlier mechanism is HYPR. Not sure why its UI stays up.

SFAuthorizationPluginView and MacOS Tahoe
 
 
Q