Skip to content

macOS 3.7: "Starting an exam" config won't launch the exam — reconfigures/restarts on file open, locks up and returns to portal on seb:// link #630

Description

@menziesrm

Describe the bug

On macOS (SEB 3.7), a .seb configuration file whose purpose is "starting an exam" (sebConfigPurpose = 0) fails to start the exam session, via two different launch paths:

Double-clicking the .seb file: SEB processes it through the client-reconfiguration path (reconfigureClientWithSebClientSettingsCallback) and immediately quits to restart (sessionQuitRestart restart: 1). After the restart SEB does not enter Assessment/kiosk mode — the normal desktop and other apps stay visible, only the SEB menu-bar title appears, a "Location Services Required for Wi-Fi" prompt shows, and the start URL never loads. Every attempt produces an identical ~20-line log ending at the restart trigger.
Launching via seb:// link from the exam portal: the same config fails to start the exam — SEB locks up and returns to the same portal page instead of entering the exam session.

Launching SEB directly from the Applications folder (using already-stored client settings) works correctly and loads the exam portal in full lockdown. The failure occurs only when launching via the config file or the seb:// link.

To Reproduce

Path A — config file:

On a Mac with SEB freshly set up, double-click the "starting an exam" .seb file.
SEB shows the "SEB Re-Configured" dialog and quits to restart.
SEB relaunches but does not enter Assessment/kiosk mode — normal desktop and apps remain visible, a "Location Services Required for Wi-Fi" prompt appears, and the start URL is not shown.
Re-clicking the config file repeats the same reconfigure-and-restart with no exam session (reproduced 8× in the logs).

Path B — seb:// link:

From the exam portal, click the seb:// link that launches the same 3.7 exam config.
SEB locks up and returns to the same portal page instead of starting the exam session.

Expected behavior

Both launch paths should apply the settings and start the exam session — entering Assessment/kiosk mode and loading the configured start URL (https://e-exams.sace.sa.edu.au/...), the same locked-down state that a direct launch of SEB from the Applications folder produces.

Screenshots

The "Location Services Required for Wi-Fi" prompt shown after the file-open launch (SEB running but not locked down, with the normal desktop visible behind it).

Version Information

OS: macOS [macOS 26.2 and 26.6]
SEB Version: [SEB 3.7 build 1591F]

org.safeexambrowser.SafeExamBrowser 2026-08-11--02-42-42-110.log
org.safeexambrowser.SafeExamBrowser 2026-08-11--02-40-18-792.log

Additional Context

Reproducible on every config-file launch and every seb:// launch on this machine; direct launch of SEB from /Applications works, so the app install and permissions are functional.
Config settings: sebConfigPurpose = 0 (starting an exam), lockdownModePolicy = 0 (Automatic, so AAC is selected on supported macOS), allowWlan = true (source of the Location Services prompt), aacDnsPrePinning = false, minMacOSVersion = 0. Authored with originatorVersion = SEB_iOS_3.7_1591F.
The file-open path is logged as being processed via reconfigureClientWithSebClientSettingsCallback with a pwcc outer prefix, even though the config's purpose is "starting an exam" (0). Worth confirming whether a purpose-0 file should ever take the client-reconfiguration path.
Possibly related to the 3.7 release-note item: "When reconfiguring from SEB settings which have AAC active … some system alerts were hidden. This mostly applied to the macOS Screen Recording and Accessibility permissions dialogues. SEB was then stuck…" — the reconfigure → restart → no-lockdown sequence here resembles that path.
Granting Full Disk Access + Location Services and rebooting did not change the behaviour.
For Path B, confirm the exact scheme used by the portal link (seb:// vs sebs://), as it affects how SEB fetches the config.
Logs available from ~/Library/Logs/Safe Exam Browser/ (8 file-open sessions; a log from a seb:// attempt should be captured separately as its path differs). A password-scrubbed copy of the config can be provided. A SACE demo/test login may be needed to fully reproduce the post-lockdown page load — advise if required.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

in pre-release versionplease testThe issue was solved in a beta/preview version, please test if it works for you.

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions