How do you fix the error "The font .AppleSystemUIFont is missing"

Timecode's solution worked for me too. Thanks!

1. Make a copy of the file you're having issues with
2. [Using the OS X i.e. desktop version of Numbers] Open the file containing the issues
3. Select, File > Export To > Numbers '09
4. Save your Numbers '09 version somewhere temporary for now (like your desktop)
5. Open the temporary Numbers '09 version of your file
6. Hit command-S (i.e. save)
7. Select 'Upgrade' from the dropdown sheet
8. Marvel at the fact that everything is now as it should have been! [Verify this by closing the file and re-opening it, noting there are no more warnings or issues]
9. Finally, once you're happy that everything is fully working with the new (temporary) file, simply delete or overwrite the old original [drag drop onto it if you haven't changed the name].

I just tried this and it worked fine for me, too. It seems like Apple could fix this annoying problem very easily so we don't have to use this trick.

Thank you very much, Timecode. I followed your instructions and everything worked perfectly! This was driving me nuts as I didn't want to just hide the problem, I wanted it fixed.

"It seems like Apple could fix this annoying problem very easily so we don't have to use this trick."

Numbers menu > Provide Numbers Feedback

Send a bug report.

Describe the issue.

Describe the steps necessary to make it happen.

Request a bug fix.

Regards,

Barry

despite Timemachine's solution, it's tricky to export and import your files and assume that the documents are fine without checking.

Simple documents don't take much time, but more complex files (cross-linking formulas between pages) do take some... 😐

Maybe a 'find a replace font' would be a good feature to add in Numbers, Pages and Keynote.

Although I don't know it would fix this issue.

Applecompot wrote:

despite Timemachine's solution, it's tricky to export and import your files and assume that the documents are fine without checking.

Simple documents don't take much time, but more complex files (cross-linking formulas between pages) do take some... 😐

Maybe a 'find a replace font' would be a good feature to add in Numbers, Pages and Keynote.

Although I don't know it would fix this issue.

Agree. I don't think that the conversion method is a reliable fix or a work-around. It can break things in your document. Additionally it removes table styles and paragraph styles as well as formula formatting.

As I mentioned before, formulas with time and duration can be broken after conversion. I've reported this issue a while ago but unfortunately it hasn't been fixed. So please check your tables after conversion.

Before:

After:

I get this on MOST of my spreadsheets in Numbers, so it is a trivial but regular irritation.

Anyone got a system-wide fix yet?

Applecompot wrote:

despite Timemachine's solution, it's tricky to export and import your files and assume that the documents are fine without checking.

Simple documents don't take much time, but more complex files (cross-linking formulas between pages) do take some... 😐

Maybe a 'find a replace font' would be a good feature to add in Numbers, Pages and Keynote.

Although I don't know it would fix this issue.

Cause this "error" doesn't affect any of the data or layout of my spreadsheets I didn't look for fixing this problem. But since I had some spare time, I looked at the file-structure of one of those affected documents.

The mentioned .systemIU Font is used in stylesheet of the document which is found in the underlaying directory --> 'filename'.numbers/Index/DocumentStylesheet.iwa

Because this fragment (.iwa-file) is part of a serialized index.zip file, it can't be rewritten and the .zip-file recomposed, without Numbers refusing to open the newly created file.

It's either using the 'export to Numbers09' - work-around or waiting and hoping that this issue is picked up by Apple's Numbers programmers on a next upgrade.

10.11.1.is old, 10.11.6 is current.

@ Csound1:

"10.11.1.is old, 10.11.6 is current."

Original post was within 10 days of the 10.11.1 update. 10.11.1 was still current on Nov 9, when s.beric's post (to which your reply is directed) was made. 10.11.2 update wasn't released until Dec 8.

Apparently the issue still exists.

Regards,

Barry