Issue Description
If you see Self Service crashing on launch, this can be caused by a broken configuration profile or policy.
Troubleshooting
Check the Self Service logs on the end users device (~/Library/Logs/JAMF/selfservice.log).
If you see something similar to the log below, which shows a 500 error for URL: https://jamf_url_here:8443/ssapi/V1/ssmacos/objs/configProfile
[2021-07-02 10:10:47] Request completed:
data: Optional("{
\"httpStatus\" : 500,
\"errors\" : [ ]
}")
response: Optional("<NSHTTPURLResponse: 0x60000174a1c0> { URL: https://jamf_url_here:8443/ssapi/V1/ssmacos/objs/configProfile } { Status Code: 500, Headers {
\"Cache-Control\" = (
\"no-store, no-cache, must-revalidate, max-age=0, post-check=0, pre-check=0\",
\"no-cache, no-store, must-revalidate\"
);
Connection = (
close
);Go through each policy and configuration profile in Jamf Pro and attempt to locate ones that either don't load at all or have red error highlighting on the payloads for said profile.
Remove the items that do not load from Jamf.
Take a screenshot first if needed to recreate.
For configuration profiles - remove all devices from Scope.
Click Delete in the bottom right corner.
Recreate the profiles/policy if needed.