Locking keeps an existing session in place.
The intended Lunlo moment starts after you have signed in to your Mac and launched the app. When that session is locked, a deliberate scan would request membership verification, process the enrolled face locally and, if every required check passes, attempt to enter the saved Mac password.
This depends on more than the appearance of a password field. The app needs the right session, an authorized local vault, usable camera access and a current account decision. A screenshot of a lock screen cannot establish those conditions.
Check which kind of sign-in you are seeing.
| Situation | What it means for Lunlo |
|---|---|
| An existing session is locked | The target use case, with the app running and all checks satisfied. Real unlocking remains unverified. |
| The Mac has restarted | Use normal macOS startup login. Lunlo does not provide the first login. |
| You logged out | Lunlo does not sign in to a logged-out user session. |
| FileVault asks for startup credentials | Use the Mac’s normal FileVault authentication. Lunlo does not operate before that step. |
| The Mac wakes from sleep | The display waking alone is not enough; the existing session and app checks still determine eligibility. |
FileVault protects access to the startup disk.
Apple describes FileVault as an additional protection that requires login credentials to access encrypted data. Lunlo runs inside a user session and does not replace that startup protection. See Apple’s explanation of how FileVault works.
Keep the normal Mac sign-in route available. Turning off FileVault would not make Lunlo a supported startup-login tool and is not part of its setup.
Start troubleshooting with the session state.
First identify whether this is startup, logout, FileVault or a locked session. Then check the release status: accounts and public downloads are currently closed. Once a configured release exists, the setup guide and permissions guide describe the other prerequisites.