From Xcode plugin to Xcode extension
summary
Explains how old Xcode plugins accessed private frameworks to do things like add a mini-map and live color previews, and how Apple locks that down so extensions can only edit the current file. Shows a working path: use a cosine tool to create a self-signed signature so a modified Xcode loads plugins, and a fallback that uses AppleScript sandbox workaround to install helper scripts and surface color-literal previews and open-project actions, but Mojave permission prompts limit the approach.
AI-written summary · about
chapters (7)
- 0:00Introduction
- 1:08Xcode plugins overview
- 3:18Technical details of plugins
- 5:55Xcode extensions introduced
- 7:41Moving plugins to extensions
- 10:27App sandbox and security
- 11:32macOS Mojave changes
related talks
28mWorking with XcodeKit
04mThere is an extension for that
01h 08mPlaying With the Limits: Can Your App Run Arbitrary Binary
23miOS Home Depot (A Tooling Talk)
26mNo More Anxiety: How to Use iOS Extensions in Your Flutter App
45mTooling in Swift - Xcode Integration & CI
29mHunting Malicious IDE Extensions: Building Detection at Scale... (Vinod Tiwari)
34mHacking Marzipan, Running iOS apps on Mac