It happens to me quite often that when I am testing a plugin, nothing happens. I get told that last time I opened Glyphs, the plugin crashed, but I don’t know why. Nothing in the Macro window, nothing obvious in the Console log. I do all the usual things - comment out bits of code, make sure MacOS/plugin is the latest version, replace the plugin.py with the template file, … nothing. It just crashes and I have no idea why.
Please, when Glyphs knows that a plugin recently crashed, could it log more diagnostic messages when loading that same plugin next time? Like, something in the Console log before and after the plugin binary is loaded, messages before and after each call to a method on the plugin, log the return value of each method, etc.
$ codesign -v Python\ Templates/Reporter/____PluginName____.glyphsReporter/Contents/MacOS/plugin
Python Templates/Reporter/____PluginName____.glyphsReporter/Contents/MacOS/plugin: code object is not signed at all
The plugins don’t need code signing. You only need to get them past Gatekeeper. So if you download them through Safari or send them by Mail, you need to strip the quarantine bits. Glyphs is doing that when you “install” it. Just putting them in the Plugins folder will not work. But getting them through git is fine.
Then you start Glyphs from the terminal: /Applications/Glyphs 3.app/Contents/MacOS/Glyphs 3 you should see some log message about the failing plugin.
I’m starting to wonder if it’s my installation - just installed a few plugins from the Plugin Manager; Backdrop and Show Rotated also crashed, with nothing obvious on the console.
I’m using Glyphs’ 3.9.1. But what I’ve found is that if Glyphs installs them via the package manager, they don’t work. If I git clone the repositories myself, they work.