What should I do if the Xcode plugin cannot be installed?

**The following package file: Open the direct build, and then restart the xcode plug-in to automatically install the installation location: library application support developer shared xcode plug-ins If you want to uninstall it, find the location to delete it.

In fact, the idea is to find the file directory of these xcode plug-ins, delete it and reinstall it. However, these file directories are usually hidden.

The second step is to find the directory of these files, users kaynel library (the first three are, finder -> go to -> personal -> resource library (the gray one is it)) application support developer shared xcode plug-ins, delete the plugins in this directory, alcatraz don't delete them, it's to manage plugins, The others are plug-ins that you have installed but have not successfully installed, and you can delete them at will.

Step 3: Open Xcode, Command Shift 9, search for the plug-in you want in the pop-up box, and install it.

Step 4: Exit xcode completely, restart xcode, a box will pop up, click loadbundle, ok, congratulations, the plugin is available!

<>2. Click Open when you're donedmg" format file, and then double-click on the xcode file to start the installation. In the dialog box that appears, click Continue.

<>4. In the pop-up product catalog dialog box, you can see the program to be installed and start the installation.

5. Enter the username and password in the pop-up dialog box, and click the "OK" button.

6. In the pop-up new dialog box of Qinhui, the installation progress is displayed, and the installation is completed.

<>2. Click Open when you're donedmg" format file, and then double-click on the xcode file to start the installation. In the dialog box that appears, click Continue.

<>4. In the pop-up product catalog dialog box, you can see the program to be installed and start the installation.

5. Enter the username and password in the pop-up dialog box, and click the "OK" button.

6. In the pop-up new dialog box of Qinhui, the installation progress is displayed, and the installation is completed.

One. The reason why the Xcode plug-in fails.

It's not that the original plug-in has been deleted after upgrading or reinstalling, in fact, the plug-in is still in this directory Library Application Support Developer Shared Xcode Plug-ins. The reason why the plug-in is invalid is that each plug-in is only used by the xcode of a specific UUID, and the UUID changes after the update, so it cannot be used normally.

Two. Solution.

1.View the UUID of the current XCODE

Running the defaults read applications dvtplugincompatibilityuuid in the terminal will get a string of uuid codes. Maybe your xcode is not installed by you, but directly copied the xcode installed by someone else into your application, then this command will not get the uuid of xcode

Another way is to get the UUID of XCODE, find XCODE in the application, right-click to display package content, find the file and open it, and find the value corresponding to the DVTPLUGINCOMPATIBILITYUUID is the UUID we want

2.Change the UUID of the plug-in to the UUID of the current XCODE

Find this directory Library Application Support Developer Shared XCode Plug-ins, find the corresponding plugin, right-click to display the package content, find the file to open the vtplugincompatibilityuuids project, add an item, the value is the UUID of the previous xcode, and save.

3.You'll be prompted after restarting Xcode"load bundle"、 skip bundle", which must be chosen here"load bundle", otherwise the plugin cannot be used. If you accidentally click on the skip bundle again, delete the item line you just added in the plugin plist file, restart Xcode, and then repeat the previous steps.

At this point, the problem has been solved perfectly.

1. Update Xcode, the latest version is;

2. Since installing the plug-in will affect the original xcode packaging and upload, we will copy an xcode in the application and rename it to xcodesigner;

3. Open the keychain, create a new certificate, fill in the name xcodesigner, and select the certificate type as code signing;

Create a certificate. Enter the certificate information.

4. Enter sudo codesign -f -s xcodesigner applications in the terminal command, and wait patiently for the execution of the order to be executed;

5. Obtain the UUID of xcodesigner, and enter :

Select XCODesigner as the opening method.

7. Check whether the UUID obtained in step 5 has been added, and failure to add it may cause XCODESIGNER to flash and reject. If the file already exists, you can run the project directly;

Add the uuid in

8. After the operation is successful, close xcodesigner and restart, then the following two types of prompt boxes will pop up, the branch source base selects load bundle and commotion allowed (or always allowed), then click the window to see that there are more esjsonformats in the list.

Select Load Bundle

Select Teasing Allowed.