SFUnlock UI changes in macOS Golden Gate Beta – OK button requires double-click after password entry

Question

Created 5d

Replies 3

Boosts 0

Participants 2

We have observed significant UI changes to the SFUnlock login experience in the latest macOS Golden Gate Beta.

After entering the account password at the SFUnlock screen,user has to click on Use Password button once and then click on the OK button to proceed to the desktop and for the login process to continue successfully. This behaviour is consistently reproducible in our testing.

We would like to understand:

1.Is this a known issue with the current macOS Golden Gate Beta?

2.Is this expected behaviour due to the UI redesign, or is it considered a bug?

3.If it is a known issue, is there a fix planned for an upcoming beta or the final release?

Any information or guidance would be appreciated. Thank you.

Answered by DTS Engineer in 900882022

Thanks for confirming that.

IMO you should file a bug about this. It doesn’t really matter whether this is by design or not, because you have an existing product that’s having problems on the beta. So either:

If it’s by design, your bug report can act as a request to reconsider that design.
If not, it can act as a normal bug report.

Please post your bug number, just for the record.

As always, include a sysdiagnose log with your bug report, taken on the machine with the problem shortly after reproducing it. It’d also help if you attach screenshots of what you see on macOS 26 and what you see on macOS 27 beta.

I typically test this stuff on a VM, where it’s easy to get a screenshot by triggering it on the host. If your testing this on real hardware, you can SSH in and take a screenshot using the screencapture tool.

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

Answer 1

DTS Engineer OP

Apple

5d

I’d like to clarify what you mean by “SFUnlock UI”. There’s no SFUnlock symbol, so I suspect you’re using this as a shorthand for something. Are you talking about:

An authorisation plug-in
With a mechanism that you install into system.login.screensaver
That uses SFAuthorizationPluginView to present a custom UI to unlock the screen?

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

Answer 2

PrathibhaD OP

5d

Yes , I meant the SFAuthorizationPluginView of MAC. We are trying to authenticate-session-owner-or-admin in system.login.screensaver authorisation db.

Answer 3

DTS Engineer OP

Apple

2d

Recommended

Thanks for confirming that.

IMO you should file a bug about this. It doesn’t really matter whether this is by design or not, because you have an existing product that’s having problems on the beta. So either:

If it’s by design, your bug report can act as a request to reconsider that design.
If not, it can act as a normal bug report.

Please post your bug number, just for the record.

As always, include a sysdiagnose log with your bug report, taken on the machine with the problem shortly after reproducing it. It’d also help if you attach screenshots of what you see on macOS 26 and what you see on macOS 27 beta.

I typically test this stuff on a VM, where it’s easy to get a screenshot by triggering it on the host. If your testing this on real hardware, you can SSH in and take a screenshot using the screencapture tool.

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