Yep, as a long term macOS user, I’m aware of that. Thanks for the absolute path to the dll. Entering this when prompted for an unresolved reference solved the issue I had!
@DanielPiker, @dan, entering the path into the dialogue, instead of the whole app renaming business seems to be a better, less unprofessional idea (for a pro app)!!
Another long-term solution could simply be to make Rhino/Grasshopper aware of where official dependencies (like K2) are located on Windows AND macOS, so that it knows what to chose in each case. Seems to work fine on Windows…
Another curiosity is that the IMG (Import Image) component seems to differ between the Windows and Mac version. I couldn’t get the component from Daniel’s file to run without errors, however when I replaced it, it worked fine.