Skip to main content

Started noticing this on machines for my enrollment script using jamfhelper.

 

Doesnt seem to have any real bearing on outcome as the text prompts still show up, but in the logs, most, if not all, jamfhelper prompts are followed by com.apple.fonts not accessible.

 

Excerpt from log with macOS Monterey with M1 pro

 

Log from M1 with macOS Big Sur

 

 

Any ideas why this is a thing?

 

 

 

How did you scale it to deployed macs? pushed the new cert to all macs?


We just have a single Mac that we deploy to, so I VNC-ed in and updated it manually via keychain. You have many mac build machines? Do you use some kind of image?

Edit: I just realized I didn't even know what jamf is, just arrived here because of the similar error. You may have to delete the old certificates, as well.
 

I found that the fontd daemon wasn't running - so ran

launchctl load -w /System/Library/LaunchAgents/com.apple.fontd.useragent.plist

which fixed it.

I've only started looking today, but I've found several open threads concerning this problem:

What I'm noticing is some discussion about secure tokens from the Apple Developer Forum threads. In one example someone was trying to load a Launch Daemon to have software updates install, but it also encountered a hung state that reads (to me) similarly to the symptoms mentioned in the MunkiTools thread. It seems like the connection between com.apple.fonts and Software Updates are the notifications presented to the user when the sequence is started and/or ready to restart. There are a lot of mentions of Secure Tokens being an issue, and while I didn't think of that at first, that seems as good a place as any to start. If I come up with anything on that front I'll share it here. 

  •  

in replying to @The_Black_Rose i'm having the same issue with Monterey 12.3 wanting to upgrade to 12.6 via terminal using the softwareupdate command and it didn't work, i also got the error message below

softwareupdate[17905:571877] XType: com.apple.fonts is not accessible.

i don't think this is related to secure token because i ran the following command: 

sysadminctl -secureTokenStatussysadminctl -secureTokenStatus localadmin and it returned:

Secure token is ENABLED for user localadmin

so as you can see, it's not that but Since Monterey apple have definitely broken the softwareupdate comand!! The only way i could update from 12.3. to 12.6 was via the usual UI update tool.

I was having a similar issue with a custom app that pushes a local notification. It was working fine when I ran the script locally, but as soon as it was run by Jamf, it failed with this XType error.

The problem was that the custom application was run in root context. The fix is to run it in the users context:

sudo -u "$CURRENT_USER" open -a "$NOTIFY_APP" --args "Software Update Notification" "$applicationName needs to be updated!"
 
Thanks I will try this!

HARTE QUIMBY | ASSOCIATE DESKTOP ENGINEER
My SLEEP NUMBER® setting is 40. What’s yours?
P 763.551.6284
harte.quimby@sleepnumber.com

SLEEP NUMBER
1001 Third Avenue South, Minneapolis, MN 55404
sleepnumber.com | facebook.com/sleepnumber

This worked for me too!!! Thank you for the suggestion.

 

The thing that I think finally solved it was installing the correct "Apple Worldwide Developer Relations Certification Authority" in Keychain. The one I had had an expiration date of February 2023. I deleted that one and went here: https://www.apple.com/certificateauthority/, downloaded the one called "Worldwide Developer Relations - G3 (Expiring 02/20/2030 00:00:00 UTC)", then retried the build and it worked.


What method do you use to deploy the Apple certificate- Composer?  

Terms & ConditionsCookie settingsAccessibility statement