Step 1: download the project
Clone the project: plug-in , close it after running the project;
Step 2: terminal execution
Execute defaults read /Applications/Xcode.app/Contents/Info DVTPlugInCompatibilityUUID in the terminal first, and then copy the string;
Step 3: enter the Finder
1) Click Finder to go to the directory: ~/Library/Application Support/Developer/Shared/Xcode,
2) Find the VVDocumenter-Xcode plugin to display the package content,
3) Enter the Contents folder and open Info.plist;
4) Find: DVTPlugInCompatibilityUUIDs, add New item and copy the previously copied string;
Step 4: exit Xcode
Now completely close Xcode, and then restart Xcode, it will prompt "Load bundle", "Skip Bundle", here you must select "Load bundle".
Step 5: automatic output
If you enter "///" in different positions of the project, different results will be automatically output, try it yourself!
Xcode installation plugins often encounter such problems. There are prompt choices, or English prompts, so I habitually choose the button on the right without looking carefully.
I clicked Skip Bundle, and it was found tragically that the plugin was completely invalid. No matter how to open Xcode in the future, how to reinstall the plugin, the probability of reappearing is very low.
Principle and reason
The principle is very simple. Mac os stores the choice of whether you are allowed to load a third-party plug-in in Xcode preferences, which is actually Userdefault, so in iOS development. You can enter the following commands through the command line Let’s show it again! It’s actually clearing the preferences on Xcode
The Load Bundles method reappears
1. Terminal command to clear Xcode third-party plugin preferences