Hello everyone,
I'm just sharing my fix for a problem I got since I switched to Self Service+ (SSP). I'm not sure if others have encountered this but it affects all our Macs (40+) so it's definitely not isolated.
Hope this can help and I'm open to any discussion on the matter.
Environment
Self Service+ 2.16 via jamf pro (Use Self Service+ as the default end user application)
Symptoms
Self Service+ would quit and relaunch itself every time a standard user executed any policy (or when doing a check-in). Admin users were unaffected.
Root cause
When you rename Self Service+ through custom branding (via the cli as explained in the official docs), the app bundle name changes, but the jamf binary preference key self_service_plus_path in /Library/Preferences/com.jamfsoftware.jamf.plist still points to the old path /Applications/Self Service+.app.
When a policy executes, the jamf binary tries to send the completion callback back to SSP via XPC using that stale path. It can't find the process, logs Connection invalid - No such process, and the callback fails. SSP never receives the completion signal, causing it to quit. The LaunchDaemon then relaunches it.
Fix:
I set up a script trigger at login to rename SSP and modify the jamfsoftware plist:
selfservice branding brand --name "Our Store Name"
sudo defaults write /Library/Preferences/com.jamfsoftware.jamf.plist self_service_plus_path "/Applications/Our Store Name.app"
The login trigger is recommended since Jamf updates or reinstalls of SS+ may reset the plist to the default path, requiring the fix to be reapplied.