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.

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.

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?

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.

I have the same issue with macOS 26. Not sure about earlier OS versions. You may consider using a short form UUID instead (four hex bytes) from the private range if possible. Otherwise, you would need to add a read characteristic for the central to query the name.

I don't set LimitLoadToSessionType. My launch agent is not a GUI app. I'm thinking that may be an issue.