How should Alcatraz handle plugins in the skipped bundles list

[Ashton-W]

See #281 #282

The above issue is about resolving Alcatraz itself being in the skipped bundles list. How should we handle Alcatraz installed plugins being in the skipped bundles list?

We could include a script to remove the plugin's entry upon install, giving similar behaviour to the proposed solution for Alcatraz itself.

Alcatraz should probably be aware of which installed plugins are being prevented from loading, so in the plugins list UI we can inform the user and give instructions to fix it ("Fix issues").

[guillaumealgis]

My opinion is that such plugins should appear in the list, but with a different button state. Something like this:

Clicking the "Blocked" button would remove the plugin from the skipped list, restoring it to the installed state.

---

On a side note, I think plugins not yet supported in the user's Xcode version (ie. plugins not having the right Xcode UUID in their Info.plist) should behave similarly

Clicking on the button then does nothing (or maybe explain what is going on), and maybe alt-clicking force-installs the plugin by modifying the Info.plist with the current Xcode UUID.

This would (hopefully) prevent the rise of opened issues for each Xcode release, and the use of dirty hacks like the find | xargs | plutil script to add the Xcode UUID to all plugins.

[jurre]

Yes, I agree with @guillaume-algis, thanks for the detailed writeup!

[guillaumealgis]

FYI, I started implementing this on https://github.com/guillaume-algis/Alcatraz/tree/feature/xcode-blacklist

[arturgrigor]

I've implemented this script to automatically mark all the 3rd party installed plugins as compatible with a version of Xcode because I was tired of editing the Info plists on every update. Check it out, maybe it helps, because Alcatraz isn't the only problem, all the previously installed plugins must be allowed to run after an Xcode update.

https://github.com/arturgrigor/ForceLoadXcodePlugins