MacOS Self Service crashes instantly - com.apple.main-thread

apple21
New Contributor

Hello everyone,

our team currently experiences a Problem with the Self Service on a few (2-3 of 2000+) Macs, where the Self Service App instantly crashes when opened.
Till now we tried the following things:
- Restart the Mac πŸ˜‰
- Delete Self Service manually and let it reinstall via sudo Jamf Recon/Policy
- Scanned the App with the "App Cleaner" and deleted all the .plists etc. with the App
- reload the Jamf binary on the Mac
- tired a different User Account on the Mac
but all those Actions did not solve the Problem.

We reinstalled MacOS on one of those Macs. This fixed the problem, till now. It started to crash on one of those Mac again.
Does anyone has an Idea, what this could cause?
A quick Google Search showed, that "SIGILL" seems to be a Swift Trap?

Thanks a lot!

Log:

Process: Self Service [44279]
Path: /Applications/Self Service.app/Contents/MacOS/Self Service
Identifier: com.jamfsoftware.selfservice.mac
Version: 10.24.2 (10.24.2-t1600451425)
Code Type: X86-64 (Native)
Parent Process: ??? [1]
Responsible: Self Service [44279]
User ID: 1074589388

Date/Time: 2020-10-13 15:12:59.588 +0200
OS Version: Mac OS X 10.15.7 (19H2)
Report Version: 12
Bridge OS Version: 4.6 (17P6610)
Anonymous UUID: C89A62C3-EF8F-4B0A-A578-8D488F4A5536

Sleep/Wake UUID: 11D438E2-BCEB-4F8E-AA9E-0E822DE36D35

Time Awake Since Boot: 100000 seconds
Time Since Wake: 28000 seconds

System Integrity Protection: enabled

Crashed Thread: 0 Dispatch queue: com.apple.main-thread

Exception Type: EXC_BAD_INSTRUCTION (SIGILL)
Exception Codes: 0x0000000000000001, 0x0000000000000000
Exception Note: EXC_CORPSE_NOTIFY

Termination Signal: Illegal instruction: 4
Termination Reason: Namespace SIGNAL, Code 0x4
Terminating Process: exc handler [44279]

Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
0 com.jamfsoftware.selfservice.mac 0x0000000103780ee1 0x1036a2000 913121
1 com.jamfsoftware.selfservice.mac 0x0000000103780965 0x1036a2000
911717
2 com.jamfsoftware.selfservice.mac 0x000000010378098f 0x1036a2000 911759
3 com.jamfsoftware.selfservice.mac 0x0000000103741283 0x1036a2000
651907
4 com.jamfsoftware.selfservice.mac 0x0000000103741d6f 0x1036a2000 654703
5 com.jamfsoftware.selfservice.mac 0x000000010372a2d2 0x1036a2000
557778
6 com.jamfsoftware.selfservice.mac 0x00000001037280b0 0x1036a2000 549040
7 com.jamfsoftware.selfservice.mac 0x000000010372a1fd 0x1036a2000
557565
8 com.apple.CoreFoundation 0x00007fff3118480f CFNOTIFICATIONCENTER_IS_CALLING_OUT_TO_AN_OBSERVER 12
9 com.apple.CoreFoundation 0x00007fff311847a3 ___CFXRegistrationPost1_block_invoke
63
10 com.apple.CoreFoundation 0x00007fff31184718 _CFXRegistrationPost1 372
11 com.apple.CoreFoundation 0x00007fff31184384 ___CFXNotificationPost_block_invoke
80
12 com.apple.CoreFoundation 0x00007fff311544fd -[_CFXNotificationRegistrar find:object:observer:enumerator:] 1554
13 com.apple.CoreFoundation 0x00007fff311539a9 _CFXNotificationPost
1351
14 com.apple.Foundation 0x00007fff337d1786 -[NSNotificationCenter postNotificationName:object:userInfo:] 59
15 com.apple.AppKit 0x00007fff2e3ef869 -[NSApplication finishLaunching]
330
16 com.apple.AppKit 0x00007fff2e3ef3f0 -[NSApplication run] 244
17 com.apple.AppKit 0x00007fff2e3c1396 NSApplicationMain
777
18 com.jamfsoftware.selfservice.mac 0x00000001036a3cc9 0x1036a2000 7369
19 libdyld.dylib 0x00007fff6b228cc9 start
1

7 REPLIES 7

Hasanbasic
New Contributor

We get the same issue but only when Self Service is launched for the first time and on Big Sur. Catalina does not have this issue. The same error is described as above. Termination Signal: Illegal instruction: 4
Termination Reason: Namespace SIGNAL, Code 0x4
Terminating Process: exc handler [44279]

bowarmbold
New Contributor

We just had this issue today with a fresh install of Big Sure (11.2.1) Anyone having any luck getting it back up and running?

JustDeWon
Contributor III

It's not crashing for us. However, on macOS Big Sur(11.2.1), our Self-Service isn't caching the login credentials in keychain. There is also not a "Login" button.

We're on Jamf 10.25.2.

Vad3r
New Contributor II

Did you ever find a resolution for this? Just experiencing it now on a room full of 20 machines, 3 of which seem to be working fine with no difference on hardware spec of setup process.

thta
New Contributor II

Same issue here found the following in the system.log

Any solutions?

Jun 22 08:42:01 macbook-air com.apple.xpc.launchd[1]: Coalition Cache Hit: app<application.com.jamfsoftware.selfservice.mac.50173.50476(501)> [788]
Jun 22 08:42:01 macbook-air com.apple.xpc.launchd[1] (application.com.jamfsoftware.selfservice.mac.50173.50476[2095]): Service exited due to SIGABRT

Kingfisher678
New Contributor II

Just had this same issue and this seemed to fix it.

PI-009903 - Self Service crashes if categories assigned to an item over 32 characters

Expected Results
We can select the category from the left menu

Actual Results
Self service crashes

Workaround
- Keep categories at or below 32 characters

OR

  • Use Browse > all section versus selecting the category in self service to view available items

OR

  • Use Browse > use arrow keys to navigate to categories with more than 32 characters

Solved: Self Service Crashing - Jamf Nation Community - 239219

thta
New Contributor II

Solution for me was that the custom icon for Self Service wasn't following Jamf's size. Fixed that and everything worked.