Mac Font Book validation error after upgrading to 10.11.5

Hi there,

This is my first project I am using Glyphs with. Now I ran into this wired error - and I do not know how to deal with this. I hope you can help with this.

When I install the font on a Mac with System 10.11.5 Font Book brings up an error that looks like this:

If I continue with the installation another message pops up that says it is really dangerous to install the font.
However after continuing with the installation the font shows up and works just fine as expected. When I then select the font in Font Book and run Font Validation again this message pops up:

The same error happens when exporting to otf or ttf, as well as using Glyphs 895 or 904 to build the file.
I was not able to reproduce this error on two other macs running 10.11.4. So I looked through the update notes of
10.11.5 (https://support.apple.com/en-us/HT206567) and found a section that noted changes to ATS regarding FontValidator:

ATS
Available for: OS X El Capitan v10.11 and later
Impact: An application may be able to execute arbitrary code with system privileges
Description: An issue existed in the sandbox policy. This was addressed by sandboxing FontValidator.
CVE-ID
CVE-2016-1797 : lokihardt working with Trend Micro’s Zero Day Initiative

When I run FontValidator (ftxvalidator -T) on Terminal with the font I get these results:

F2A3292B|1.023;UKWN;AlbertEinstein1-023-Regular
kATSFontTestTrueTypeFontData
Minor Info 
com.apple.TrueType.cmap.usability
	‘cmap’ table usability
	This test ensures the ‘cmap’ table has at least one usable subtable.
	NA
		(No messages)
com.apple.TrueType.hmtx.usability
	‘hmtx’ table usability
	This test ensures the horizontal metrics table, ‘hmtx’, is valid.
	Info 
		hmtx: Glyph 2 has a width of 1250, which is greater than the font's em (1000); this may be incorrect.
			kATSFontTestSeverityInformation
		hmtx: Glyph 3 has a width of 1001, which is greater than the font's em (1000); this may be incorrect.
			kATSFontTestSeverityInformation
		hmtx: Glyph 14 has a width of 1300, which is greater than the font's em (1000); this may be incorrect.

(–followed by hundreds of lines that are about the width of a glyph that is wider than the font’s em–)

			kATSFontTestSeverityInformation
com.apple.TrueType.loca.usability
	‘loca’ table usability
	This test ensures the glyph data location table, ‘loca’, is valid.
	NA
		(No messages)
com.apple.TrueType.name.usability
	‘name’ table usability
	This test ensures the ‘name’ table is valid.
	NA
		(No messages)
com.apple.TrueType.post.usability
	‘post’ table usability
	This test ensures the ‘post’ table is valid.
	NA
		(No messages)
com.apple.TrueType.usability
	‘sfnt’ required tables
	This test ensures the ‘sfnt’ has all the required tables.
	NA
		(No messages)
com.apple.TrueType.head.structure
	‘head’ table structure
	This test ensures the structure of the header table, ‘head’, accords with the specification.
	NA
		(No messages)
com.apple.TrueType.hhea.structure
	‘hhea’ table structure
	This test ensures the structure of the horizontal header table, ‘hhea’, accords with the specification.
	Minor 
		hhea: descent (-1400) is greater than 60 percent of the em (1000)
			kATSFontTestSeverityMinorError
		hhea: sideBearingMin (-830) is wrong; it should be -537
			kATSFontTestSeverityMinorError
com.apple.TrueType.maxp.structure
	‘maxp’ table structure
	This test ensures the structure of the maximum profile table, ‘maxp’, accords with the specification.
	Minor 
		maxp: The maxZones field is equal to 1; it should be equal to 2
			kATSFontTestSeverityMinorError
		maxp: The table's maxSizeOfInstructions field is 1000; it should be 0
			kATSFontTestSeverityMinorError
com.apple.TrueType.name.structure
	‘name’ table structure
	This test ensures the ‘name’ table is structurally sound.
	Minor 
		'name': Two name entries overlap:  name entry 1 (bytes 651-672) and name entry 4 (bytes 651-672)
			kATSFontTestSeverityMinorError
		'name': Two name entries overlap:  name entry 8 (bytes 941-955) and name entry 9 (bytes 941-955)
			kATSFontTestSeverityMinorError
		'name': Two name entries overlap:  name entry 15 (bytes 1870-1924) and name entry 17 (bytes 1870-1924)
			kATSFontTestSeverityMinorError
		'name': Two name entries overlap:  name entry 19 (bytes 2318-2346) and name entry 20 (bytes 2318-2346)
			kATSFontTestSeverityMinorError
com.apple.TrueType.glyf.usability
	‘glyf’ table structure
	This test ensures the ‘glyf’ table is structurally sound.
	Info 
		glyf: Glyph 1 has no visual appearance
			kATSFontTestSeverityInformation
		glyf: Glyph 2 has no visual appearance
			kATSFontTestSeverityInformation
		glyf: Glyph 3 has no visual appearance
			kATSFontTestSeverityInformation
		glyf: Glyph 1107 has no visual appearance
			kATSFontTestSeverityInformation
		glyf: Glyph 1108 has no visual appearance
			kATSFontTestSeverityInformation
		glyf: Glyph 1109 has no visual appearance
			kATSFontTestSeverityInformation
		glyf: Glyph 1110 has no visual appearance
			kATSFontTestSeverityInformation
com.apple.TrueType.glyf.instructions
	‘glyf’ table instructions
	This test ensures the instructions embedded in a ‘glyf’ table are sound.
	NA
		(No messages)
com.apple.TrueType.fpgm.instructions
	‘fpgm’ table instructions
	This test ensures the instructions embedded in a ‘fpgm’ table are sound.
	NA
		(No messages)
com.apple.TrueType.prep.instructions
	‘prep’ table instructions
	This test ensures the instructions embedded in a ‘prep’ table are sound.
	NA
		(No messages)
com.apple.duplicates
	Duplicate fonts
	This test verifies the presence of installed fonts with the same name.
	NA
		(No messages)

Although ftxvalidator gives out clear “Minor” errors, I could not identify major issues that would cause Font Book to recommend not to install the font… so I don’t know where to start and I am confused because the second check through font book after installing puts green hooks on everything that is mentioned in the report.

What would be the best way to deal with this?

Thank you,
Harald

Was it (or another version of it) installed previously? Then this could be a font cache problem. Are you aware of this tutorial?
http://www.glyphsapp.com/tutorials/eliminating-font-cache-problems

I followed the tutorial you’ve mentioned a couple of times including restart: with no effect. Also I attach a unique number (1-021, 1-0020, 1-019…) to the font name with every version which (I believe) should avoid caching problems.

Then I would say, it is likely just a bug in Font Book.

What would be the best way to deal with it?

I would have a look at how it installs on different machines, and different app versions of FontBook. Perhaps watch the Console when you do.

I have installed the font on three different macs (running 10.11.5(1x) 10.11.4(2x)) , the error is just reproducible on 10.11.5.

Thanks for the tip with the console. Does any of these messages indicate where to look at for a cause of the error message? Thanks in advance!

This is what shows up on the console during an attempt to install the font (dragging file onto Font Book running 10.11.5)

27/06/16 12:51:39,928 Font Book[1205]: Could not find image named 'NSImageNameStopProgressFreestandingTemplate'.
27/06/16 12:51:39,992 sandboxd[141]: ([1212]) FontValidator(1212) deny file-read-metadata /Applications/Adobe InDesign CC 2015/Fonts/AlbertEinstein1-023-Regular.ttf
27/06/16 12:51:40,011 sandboxd[141]: ([1212]) FontValidator(1212) deny file-read-metadata /Applications/Adobe InDesign CC 2015/Fonts/AlbertEinstein1-023-Regular.ttf
27/06/16 12:51:40,047 sandboxd[141]: ([1212]) FontValidator(1212) deny file-read-metadata /Applications
27/06/16 12:51:40,070 sandboxd[141]: ([1212]) FontValidator(1212) deny file-read-metadata /Applications/Adobe InDesign CC 2015/Fonts/AlbertEinstein1-023-Regular.ttf
27/06/16 12:51:40,075 sandboxd[141]: ([1212]) FontValidator(1212) deny file-read-metadata /Applications/Adobe InDesign CC 2015/Fonts/AlbertEinstein1-023-Regular.ttf
27/06/16 12:51:40,081 sandboxd[141]: ([1212]) FontValidator(1212) deny file-read-metadata /Applications

The “sandboxed” corresponds with the note from Apple regarding changes to the ATS in the update 10.11.5

When I look into the full reports of the FontValidation I get these Details:

FontValidator(1212) deny file-read-metadata /Applications/Adobe InDesign CC 2015/Fonts/AlbertEinstein1-023-Regular.ttf

    Process:         FontValidator [1212]
    Path:            /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ATS.framework/Versions/A/Support/FontValidator
    Load Address:    0x10fae7000
    Identifier:      FontValidator
    Version:         ??? (???)
    Code Type:       x86_64 (Native)
    Parent Process:  launchd [1]
    User ID:         501

    Date/Time:       2016-06-27 12:51:40.070 +0200
    OS Version:      Mac OS X 10.11.5 (15F34)
    Report Version:  8

    Thread 0:
    0   libsystem_kernel.dylib        	0x00007fff918036d2 __getattrlist + 10
    1   CarbonCore                    	0x00007fff8ad484de PathGetObjectInfo(char const*, unsigned int, unsigned int, short*, unsigned int*, unsigned int*, char*, unsigned int*, unsigned char*, unsigned int*) + 364
    2   CarbonCore                    	0x00007fff8ad482bd FSPathMakeRefInternal(unsigned char const*, unsigned int, unsigned int, FSRef*, unsigned char*) + 111**
    3   ATS                           	0x00007fff8c1c1ba7 CFURLGetFSRef + 79
    4   ATS                           	0x00007fff8c21ae6a ATSFontValidateDynamic + 72
    5   ATS                           	0x00007fff8c21a467 ATSFontValidate + 424
    6   FontValidator                 	0x000000010fae8845 FontValidatorHandler + 649
    7   CoreFoundation                	0x00007fff8bd8b628 __CFMessagePortPerform + 584
    8   CoreFoundation                	0x00007fff8bcf3019 __CFRUNLOOP_IS_CALLING_OUT_TO_A_SOURCE1_PERFORM_FUNCTION__ + 41
    9   CoreFoundation                	0x00007fff8bcf2f89 __CFRunLoopDoSource1 + 473
    10  CoreFoundation                	0x00007fff8bcea9bb __CFRunLoopRun + 2171
    11  CoreFoundation                	0x00007fff8bce9ed8 CFRunLoopRunSpecific + 296
    12  CoreFoundation                	0x00007fff8bd2b9b1 CFRunLoopRun + 97
    13  FontValidator                 	0x000000010fae8542 main + 988
    14  libdyld.dylib                 	0x00007fff8e45f5ad start + 1

    Binary Images:
           0x10fae7000 -        0x10fae9fff  FontValidator (394.4) <218c5a6a-022f-39cf-8a7b-f6308746e591> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ATS.framework/Versions/A/Support/FontValidator
        0x7fff8ad41000 -     0x7fff8b026ffb  com.apple.CoreServices.CarbonCore (1136.2 - 1136.2) <2dbafc9a-6cd6-351d-b1f4-87d81aa6d640> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/CarbonCore.framework/Versions/A/CarbonCore
        0x7fff8bc61000 -     0x7fff8c0d7fff  com.apple.CoreFoundation (6.9 - 1258.1) <943a1383-da6a-3dc0-abcd-d9aeb3d0d34d> /System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation
        0x7fff8c1bd000 -     0x7fff8c22bff7  com.apple.ApplicationServices.ATS (377) <9779e916-0788-3cac-b1ec-f68bcb12a2b6> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ATS.framework/Versions/A/ATS
        0x7fff8e45c000 -     0x7fff8e45fffb  libdyld.dylib (360.22) <cc088c2a-d407-33e7-a6b6-b06e0d4ad999> /usr/lib/system/libdyld.dylib
        0x7fff917ed000 -     0x7fff9180bff7  libsystem_kernel.dylib (3248.50.21) <78e54d59-d2b0-3f54-9a4a-0a68d671f253> /usr/lib/system/libsystem_kernel.dylib

The 5 other reports differ only vary in the first three thread lines,
with either a line saying:
1 CarbonCore 0x00007fff8ad61d6c FSGetCanonicalPath + 260
0 libsystem_kernel.dylib 0x00007fff918036d2 __getattrlist + 10
1 CarbonCore 0x00007fff8ad48439 PathGetObjectInfo(char const*, unsigned int, unsigned int, short*, unsigned int*, unsigned int*, char*, unsigned int*, unsigned char*, unsigned int*) + 199
2 CarbonCore 0x00007fff8ad484de PathGetObjectInfo(char const*, unsigned int, unsigned int, short*, unsigned int*, unsigned int*, char*, unsigned int*, unsigned char*, unsigned int*) + 364

Thread 0:
0   libsystem_kernel.dylib        	0x00007fff91804fba lstat$INODE64 + 10
1   CarbonCore                    	0x00007fff8ad61d6c FSGetCanonicalPath + 260
2   CarbonCore                    	0x00007fff8ad484de PathGetObjectInfo(char const*, unsigned int, unsigned int, short*, unsigned int*, unsigned int*, char*, unsigned int*, unsigned char*, unsigned int*) + 364

Thread 0:
0   libsystem_kernel.dylib        	0x00007fff918036d2 __getattrlist + 10
1   CarbonCore                    	0x00007fff8ad48439 PathGetObjectInfo(char const*, unsigned int, unsigned int, short*, unsigned int*, unsigned int*, char*, unsigned int*, unsigned char*, unsigned int*) + 199


Thread 0:
0   libsystem_kernel.dylib        	0x00007fff91804fba lstat$INODE64 + 10
1   CarbonCore                    	0x00007fff8ad61d6c FSGetCanonicalPath + 260
2   CarbonCore                    	0x00007fff8ad484de PathGetObjectInfo(char const*, unsigned int, unsigned int, short*, unsigned int*, unsigned int*, char*, unsigned int*, unsigned char*, unsigned int*) + 364

Thread 0:
0   libsystem_kernel.dylib        	0x00007fff918036d2 __getattrlist + 10
1   CarbonCore                    	0x00007fff8ad484de PathGetObjectInfo(char const*, unsigned int, unsigned int, short*, unsigned int*, unsigned int*, char*, unsigned int*, unsigned char*, unsigned int*) + 364

Thread 0:
0   libsystem_kernel.dylib        	0x00007fff918036d2 __getattrlist + 10
1   CarbonCore                    	0x00007fff8ad48439 PathGetObjectInfo(char const*, unsigned int, unsigned int, short*, unsigned int*, unsigned int*, char*, unsigned int*, unsigned char*, unsigned int*) + 199

After ignoring the warning message and installing the font through font book this line shows up in the console:

27/06/16 14:50:16,434 fontworker[2221]: MessageTracer: load_domain_prefix_whitelist:115: Opening whitelist file: /Library/Application Support/CrashReporter/SubmitDiagInfo.domains

followed by:

27/06/16 14:50:16,849 sandboxd[141]: ([2221]) fontworker(2221) deny file-read-data /Library/Application Support/CrashReporter/SubmitDiagInfo.domains

with this detailed report:

fontworker(2221) deny file-read-data /Library/Application Support/CrashReporter/SubmitDiagInfo.domains

Process:         fontworker [2221]
Path:            /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ATS.framework/Versions/A/Support/fontworker
Load Address:    0x10f536000
Identifier:      fontworker
Version:         ??? (???)
Code Type:       x86_64 (Native)
Parent Process:  launchd [1]
User ID:         501

Date/Time:       2016-06-27 14:50:16.433 +0200
OS Version:      Mac OS X 10.11.5 (15F34)
Report Version:  8

Thread 0:
0   libsystem_kernel.dylib        	0x00007fff91804122 __semwait_signal_nocancel + 10
1   libsystem_c.dylib             	0x00007fff89a12480 sleep$NOCANCEL + 42
2   libdispatch.dylib             	0x00007fff8e47c755 _dispatch_queue_cleanup2 + 140
3   libsystem_pthread.dylib       	0x00007fff92c6a3dc _pthread_tsd_cleanup + 555
4   libsystem_pthread.dylib       	0x00007fff92c69f63 _pthread_exit + 117
5   libsystem_pthread.dylib       	0x00007fff92c6ac0e pthread_exit + 30
6   libdispatch.dylib             	0x00007fff8e47c6ab _dispatch_queue_cleanup + 0
7   fontworker                    	0x000000010f537a5e
8   libdyld.dylib                 	0x00007fff8e45f5ad start + 1

Thread 1:
0   libsystem_kernel.dylib        	0x00007fff918043aa __sigsuspend_nocancel + 10
1   libdispatch.dylib             	0x00007fff8e47c7b5 _dispatch_sigsuspend + 0

Thread 2:
0   libsystem_kernel.dylib        	0x00007fff91804efa kevent_qos + 10
1   libdispatch.dylib             	0x00007fff8e46ddcd _dispatch_autorelease_pool_pop + 0

Thread 3:
0   libsystem_kernel.dylib        	0x00007fff91803c4a __open_nocancel + 10
1   libDiagnosticMessagesClient.dylib	0x00007fff877f02b2 msgtracer_domain_new + 387
2   libDiagnosticMessagesClient.dylib	0x00007fff877f06c1 msgtracer_vlog_with_keys + 26
3   libDiagnosticMessagesClient.dylib	0x00007fff877f08bb msgtracer_log_with_keys + 141
4   libFontParser.dylib           	0x00007fff8a99422d TFont::CreateFontEntitiesForFile(char const*, bool, TSimpleArray<TFont*>&, bool, short, char const*) + 311
5   libFontParser.dylib           	0x00007fff8a993b72 FPFontCreateFontsWithPath + 209
6   libCGXType.A.dylib            	0x00007fff94caeba9 create_private_data_with_path + 19
7   CoreGraphics                  	0x00007fff8f4f8e09 CGFontCreateFontsWithPath + 56
8   CoreGraphics                  	0x00007fff8f4f892c CGFontCreateFontsWithURL + 395
9   fontworker                    	0x000000010f537cfc
10  fontworker                    	0x000000010f5380f1
11  fontworker                    	0x000000010f539fed
12  fontworker                    	0x000000010f53a8b3
13  libdispatch.dylib             	0x00007fff8e47ca4b dispatch_mig_server + 403
14  libdispatch.dylib             	0x00007fff8e46840b _dispatch_client_callout + 8
15  libdispatch.dylib             	0x00007fff8e478675 _dispatch_source_latch_and_call + 2235
16  libdispatch.dylib             	0x00007fff8e46ca83 _dispatch_source_invoke + 983
17  libdispatch.dylib             	0x00007fff8e46d200 _dispatch_queue_drain + 1207
18  libdispatch.dylib             	0x00007fff8e473707 _dispatch_queue_invoke + 549
19  libdispatch.dylib             	0x00007fff8e46bd53 _dispatch_root_queue_drain + 538
20  libdispatch.dylib             	0x00007fff8e46bb00 _dispatch_worker_thread3 + 91
21  libsystem_pthread.dylib       	0x00007fff92c684de _pthread_wqthread + 1129
22  libsystem_pthread.dylib       	0x00007fff92c66341 start_wqthread + 13

Thread 4:
0   libsystem_kernel.dylib        	0x00007fff918045e2 __workq_kernreturn + 10
1   libsystem_pthread.dylib       	0x00007fff92c66341 start_wqthread + 13

Binary Images:
       0x10f536000 -        0x10f551fff  fontworker (155.2) <5f7d8ee9-4d98-3d7a-9e7b-c74673e07834> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ATS.framework/Versions/A/Support/fontworker
    0x7fff877ef000 -     0x7fff877f0fff  libDiagnosticMessagesClient.dylib (100) <4243b6b4-21e9-355b-9c5a-95a216233b96> /usr/lib/libDiagnosticMessagesClient.dylib
    0x7fff899e4000 -     0x7fff89a71fff  libsystem_c.dylib (1082.50.1) <b552d565-b798-3b9b-ae63-f623b42a5f01> /usr/lib/system/libsystem_c.dylib
    0x7fff8a992000 -     0x7fff8aa8eff7  libFontParser.dylib (158.6) <267a9ae4-4138-3112-8d73-bdfdc96568ff> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ATS.framework/Versions/A/Resources/libFontParser.dylib
    0x7fff8e45c000 -     0x7fff8e45fffb  libdyld.dylib (360.22) <cc088c2a-d407-33e7-a6b6-b06e0d4ad999> /usr/lib/system/libdyld.dylib
    0x7fff8e466000 -     0x7fff8e493fff  libdispatch.dylib (501.40.12) <c7499857-61a5-3d7d-a5ea-65dcc8c3df92> /usr/lib/system/libdispatch.dylib
    0x7fff8f4c8000 -     0x7fff90730ff7  com.apple.CoreGraphics (1.600.0) <0ad5ec17-569e-3864-a637-ad720f5ae0be> /System/Library/Frameworks/CoreGraphics.framework/Versions/A/CoreGraphics
    0x7fff917ed000 -     0x7fff9180bff7  libsystem_kernel.dylib (3248.50.21) <78e54d59-d2b0-3f54-9a4a-0a68d671f253> /usr/lib/system/libsystem_kernel.dylib
    0x7fff92c65000 -     0x7fff92c6eff7  libsystem_pthread.dylib (138.10.4) <3dd1ef4c-1d1b-3abf-8cc6-b3b1ceee9559> /usr/lib/system/libsystem_pthread.dylib
    0x7fff94cae000 -     0x7fff94cb0fff  libCGXType.A.dylib (957) <b901c222-e779-32eb-96c2-5a707a09fc5b> /System/Library/Frameworks/CoreGraphics.framework/Versions/A/Resources/libCGXType.A.dylib

When activating Font Validation through Font Book the dialog indicates that everything with the font is alright (see image in initial post). The console says:

> 27/06/16 14:53:42,323 sandboxd[141]: ([2271]) FontValidatorCon(2271) deny mach-lookup com.apple.distributed_notifications@Uv3
> 27/06/16 14:53:42,342 sandboxd[141]: ([2270]) FontValidator(2270) deny mach-lookup com.apple.distributed_notifications@Uv3
> 27/06/16 14:53:42,416 sandboxd[141]: ([2270]) FontValidator(2270) deny mach-lookup com.apple.lsd.mapdb
> 27/06/16 14:53:42,424 sandboxd[141]: ([2270]) FontValidator(2270) deny file-read-data /private/var/folders/h4/thbzw4gs5k151x_ns3z_19j80000gn/0/com.apple.LaunchServices-134501.csstore
> 27/06/16 14:53:42,430 sandboxd[141]: ([2270]) FontValidator(2270) deny ipc-posix-shm-read-data /tmp/com.apple.csseed.156
> 27/06/16 14:53:42,435 sandboxd[141]: ([2270]) FontValidator(2270) deny file-read-data /Users/haraldgeisler/Library/Preferences/com.apple.LaunchServices/com.apple.launchservices.secure.plist
> 27/06/16 14:53:42,440 sandboxd[141]: ([2270]) FontValidator(2270) deny file-read-metadata /
> 27/06/16 14:53:42,448 sandboxd[141]: ([2270]) FontValidator(2270) deny file-read-metadata /

Does any of these messages indicate where to look at for a cause of the initial error message from Font Book?

Can you try on another machine running 10.11.5? Can you drag the file to the Desktop before you install it?

Thanks for the tip Georg.

After dragging the font on the desktop and install it from there the error does not appear.

I got the same note about the error notification from two beta testers running 10.11.5

What could be the possible cause for the error? (In order to understand it better)
Thanks!

Some component of FontBook is not allowed to read data from none user folders. That’s what the ‘sandboxing’ warnings are about. It is strange that only some component of fontBook are effected.

Thank you very much for helping with the problem and clarification!

This is what the release notes of 10.11.5 say about changes to ATS regarding FontValidator and sandboxing:

ATS
Available for: OS X El Capitan v10.11 and later
Impact: An application may be able to execute arbitrary code with system privileges
Description: An issue existed in the sandbox policy. This was addressed by sandboxing FontValidator.
CVE-ID
CVE-2016-1797 : lokihardt working with Trend Micro’s Zero Day Initiative

Should this be brought to the attention of Apple?

Yes I get that error message too when trying to install fonts made with FL and Glyphs, must be a bug as it only started to appear after the upgrade.

I reported it to Apple and they working on it.

I have seen this issue with a small number of our fonts and like @Harald find that it only affects certain CPU builds.

Interestingly — I have managed to resolve/stop the ‘serious error’ message from appearing. Unfortunately, it doesn’t appear that there is one simple solution for all fonts. From what I have experienced the cause of this message is centred around kerning conflicts. I discovered this from dropping a glyphs exported UFO into Superpolator which in-turn generated a kern conflict error report, deeming the font unreadable.

I still don’t understand this on a deep level as yet but the fonts that had errors and that I have now fixed had:

— some kerning exceptions despite the value being the same as the group value. (Seen in FontLab Studio fonts)
— characters within kern groups even though they had a greater number of exceptions than the overall group value.

I’m still looking into it when I have the time, but it seems quite irrational FontBook behaviour.
Will keep you posted!

It is possible to post a font that can reproduce the issue? or send it to me by private/direct message?

1 Like

I had a customer that purchased my font mentioned these errors to me, and I hadn’t seen them before. I have had the fonts she purchased finished months ago. But, I found this post and now I’m concerned. Anything come of this yet? I want to figure out a solution to provide to her.

FWIW, I’m experiencing this same error on 10.12.6. Has anyone learned anything new about this?

Where is the customer installing the font from? I.e., where is the font file located when you opened it? He or she should move it to the Desktop first and double click it there.

Hi @Harald!

I just discovered this feature in the FontBook not too long ago…
It will should output the exact reason of why the validation is not passing, the result is different from ftxvalidator

  • Open the font with the Font Book app
    
  • "Install"
    
  • Wait for the validation error message
    
  • Menu: "File" > "Save Report..."
    

The report is in fact a simple “.plist” that can be opened in text mode or with Xcode.

It can help you figuring out why the validation didn’t pass but it is complimentary with ftxvalidator that is a lot more verbose.

@GeorgSeifert Hi! What is the official title of this issue by Apple? Any way to know more about it from them?

Does anyone have more info on this issue with FontBook validation errors. I’m receiving them (BigSur 11.2.2). When I review the validation report with Plist Editor I see this general warning:


And these more specific errors related to the name table: