1. Try the current version of Glyphs
There were lots of fixes and new APIs in recent Glyphs versions focused on Letterink needs so there is a good chance the issue disappears if you upgrade Glyphs. All 2.x upgrades should be free for all 2.x licence owners.
- Double check you are using an up-to-date version of Glyphs.
- If not, upgrade and try to reproduce the issue in the current version of Glyphs.
- If you have the issue again try a Cutting Edge version of Glyphs (you can enable them at Glyphs > Preferences > Updates > Show Cutting Edge Versions) and try to reproduce the issue with it.
If you have issues with upgrading, please contact Glyphs support directly at email@example.com. In order to downgrade from a Cutting Edge version to the latest stable version, uncheck Show Cutting Edge Versions and than download and install Glyphs from their website.
2. Check compatibility with other plug-ins
There are known compatibility issues between specific types of Glyphs plug-ins.
- Please check the list of plug-ins currently installed in Glyphs.
- If you use a ShowOtherMaster plug-in from Ben Syverson, please replace it with this rewritten version and check whether you still get crashes. You need to get the ShowOtherMasters.glyphsReporter.zip file from the file list as the link in the bottom text points to the original version.
- Temporary remove or uninstall all other plug-ins except Letterink and check if it still crashes. If so, the crash is not likely caused by an incompatibility between plug-ins.
- If you no longer experience crashes, install the plug-ins back one by one and test whether you get crashes after each single plug-in install. The last one you installed before the crashes reappear is most probably the one which is incompatible with Letterink. You can examine whether there are others by uninstalling the last one, skipping it and trying to install the rest one by one. Please, send us the names and versions of the incompatible plugins to firstname.lastname@example.org.
Note: In most cases, the crashes are caused by a bug in an obsolete version of PyObjC. The bug itself is fixed for a long time but Apple still ships the old version with macOS and they resist to bundle a newer one.
3. Report the issue
Sure, there might be bugs in either Letterink or Glyphs. We can discuss the reports with the Glyphs authors if we have the report details and we know which reports the right ones are.
When you start Glyphs after a crash, you should be presented by a dialog allowing you to send a report about the recent crash.
- Copy the text of the technical details and send them us to email@example.com. Please include as much details as you can, including the time you are about to send the report to the Glyphs authors, the font file causing the crash, steps to reproduce etc.
- Use the dialog functionality to also send the report to the Glyphs authors.
4. Other ideas
- Please let us know to firstname.lastname@example.org whether you noticed anything special or unusual.
- If you are able to come with a deterministic list of steps which results in a crash, please share them with us to email@example.com, including the font file if needed.
We will use your font files you send us with the bug or crash reports solely for diagnosing and fixing issues.