TL;DR Adding Swift Code to Objective-C Project Ensure your Swift class derives direct or indirect from NSObject Ensure your Swift class is public to ensure the YourProjectName-Swift.h header generation Prefix the class to expose it to Objective-C. Any Property or method needs its own @objc annotation to be visible from Objective-C. Use the @objcMembers annotation to expose all properties and methods of the Swift class Reminder for myself I learned a couple of essential things about mixing Objective-C and Swift in one project.

WFH Day 702 Well, well, well, I surpassed the 700 days since I started counting the WFH days in March 2020. That’s a long time ago, and a lot has changed in the meantime. Quality of life is better than before. No 3-hour daily commute in sticky and filthy trains, no more coffee shop visits after work, more time for reading, better-equipped work environment, not meeting some of my dearest co-workers in person anymore, taking lunch break walks, taking a nap if I don’t feel well, not seeing the dirty City anymore and feeling more productive in general.

The Gatekeeper Before I forget what I learned today, I better write it down. Gatekeeper on macOS ensures that properly signed and authentic apps and other executable files, including dylibs and kexts, are executed on your Mac. But if you want to execute an open-source tool installed by brew or some other way on your machine, you will usually see something like this confirmation dialog. In this case, for an app FSNotes installed with brew.