Xcode 5 - Required plug-in not present in DVTPlugInCompatibilityUUIDs?

Question

After upgrading Xcode to v5.0.1, I started receiving following warning in terminal when trying to run git commands inside project folder:

[MT] PluginLoading: Required plug-in compatibility UUID 37B30044-3B14-46BA-ABAA-F01000C27B63 for plug-in at path '~/Library/Application Support/Developer/Shared/Xcode/Plug-ins/Unity4XC.xcplugin' not present in DVTPlugInCompatibilityUUIDs

I am not getting any warning inside Xcode and the project is compiling just fine but there must be a reason. Any ideas why is this happening and how to fix it?

I got a very similar error just now when going from Xcode 6.? to 6.2: `2015-03-10 15:54:48.219 xcodebuild[10278:259521] [MT] PluginLoading: Required plug-in compatibility UUID A16FF353-8441-459E-A50C-B071F53F51B7 for plug-in at path '~/Library/Application Support/Developer/Shared/Xcode/Plug-ins/Unity4XC.xcplugin' not present in DVTPlugInCompatibilityUUIDs` — Jonny, Mar 10 '15 at 06:56

score 141 · Accepted Answer · edited Jan 27 '17 at 05:13

141

I modified a shell commands I found here to fix this for all my plugins.

To fix this issue:

XCODEUUID=`defaults read /Applications/Xcode.app/Contents/Info DVTPlugInCompatibilityUUID`
for f in ~/Library/Application\ Support/Developer/Shared/Xcode/Plug-ins/*; do defaults write "$f/Contents/Info" DVTPlugInCompatibilityUUIDs -array-add $XCODEUUID; done

edited Jan 27 '17 at 05:13

Shay Erlichmen

31,691
7
68
87

answered Jul 22 '14 at 01:51

ian

1,612
1
12
5

This worked for me when my builds were complaining about `OMQuickHelp.xcplugin` – Andrew Aarestad Apr 02 '15 at 19:20
3

Not working for me, I got this error: `defaults[13832:169900] Could not write domain /Users/username/Library/Application Support/Developer/Shared/Xcode/Plug-ins/Unity4XC.xcplugin/Contents/Info; exiting` – Matteo Guarnerio Jun 15 '15 at 14:18
2

If this doesn't work for you, it might be that your plugin is just a broken link which needs to be removed - that's what I had, a link to an old Unity installation that wasn't there anymore. – Adrian Demetrescu Dec 09 '15 at 19:58
If I create an alias to this in .bashrc e.g. `alias xcodeplugins='XCODEUUID=\`defaults read` etc, I get syntax error near unexpected token \`defaults'. Any tips? – David James Jan 29 '16 at 12:10
had to make a modification due to having a non-standard xcode install path. This worked for me: `XCODEUUID=$(defaults read "$(xcode-select -p)/../Info" DVTPlugInCompatibilityUUID); for f in ~/Library/Application\ Support/Developer/Shared/Xcode/Plug-ins/*; do defaults write "$f/Contents/Info" DVTPlugInCompatibilityUUIDs -array-add $XCODEUUID; done` – Idr Feb 05 '16 at 02:18
@DavidJames if you haven't gotten the alias working yet, you'd need to make these 2 lines a function and then call that function as an alias. Here's my code (and BTW this solution worked perfectly using Xcode 7.3.1) `alias fixXcodePlugins=fixXcodePluginsFunc` `fixXcodePluginsFunc() { XCODEUUID=\`defaults read /Applications/Xcode.app/Contents/Info DVTPlugInCompatibilityUUID\`` `for f in ~/Library/Application\ Support/Developer/Shared/Xcode/Plug-ins/*; do defaults write "$f/Contents/Info" DVTPlugInCompatibilityUUIDs -array-add $XCODEUUID; done }` – ubergoober May 24 '16 at 21:22
3

You might need to replace 'defaults write' with 'sudo defaults write', depending on where the plugins are located. – bleater May 26 '16 at 04:03
Thanks !! Worked for me too with Xcode 9. Mine was complaining FuzzyAutocomplete.xcplugin' not present in DVTPlugInCompatibilityUUIDs – Ammar Mujeeb Nov 16 '17 at 10:28
did not get what is the issue but by following your steps, It works. – Sagar Daundkar Jun 28 '19 at 05:13

score 44 · Answer 2 · answered Oct 08 '15 at 05:49

44

Try to do : xcode-select --install. It resolved my problem

answered Oct 08 '15 at 05:49

ion

819
10
8

5

After updating to macOS Sierra and Xcode 8.0 the plugins stopped working. This answer solved the problem. – Mani Oct 04 '16 at 06:50
1

doesn't work in new xcode if your tools are already installed. – johnrubythecat Jan 08 '17 at 06:33
1

There's a new tool out. Try `softwareupdate --list` worst case you can do `softwareupdate -a` – Jacksonkr Mar 12 '17 at 18:09
Worked!! Thanks a million. – Mike Critchley May 13 '17 at 08:08

score 31 · Answer 3 · answered Aug 12 '16 at 09:38

31

In my case of Xcode 7, remove all Xcode plugins fixed my issue.

rm -rf ~/Library/Application\ Support/Developer/Shared/Xcode/Plug-ins/*

answered Aug 12 '16 at 09:38

Quanlong

24,028
16
69
79

This did it for me as well! – Harout360 Sep 19 '16 at 19:49
2

I suspect your `DVTPlugInCompatibilityUUID` key in `/Applications/Xcode.app/Contents/Info.plist` may still have the stale UUIDs listed there even if you delete the underlying plugins. That was the case for me with an ancient plugin from 2013 that was no longer working, so I opened the plist in XCode and deleted the value from that key. – qix Oct 21 '16 at 08:10
Worked like a charm! – Aravind G S Apr 04 '17 at 06:40
Worked for me as well 2020 – Jonathan Sanchez Dec 02 '20 at 14:48
Selected answer didn't work but this worked. 2021 XCode 12.5.1 – Vincent Gigandet Aug 01 '21 at 21:23

score 6 · Answer 4 · edited Mar 13 '14 at 13:34

6

I believe the issue is that you have an Xcode plugin installed that has a missing (or has an incorrect) DVTPlugInCompatibilityUUIDs key-value pair in its plist file. See what this plugin did to solve it: https://github.com/gfontenot/XVim/commit/35bbf24bc074e330a9bea852c190d8fdcbfff1ea

Maybe check if your plugin (looks like it's for Unity) has an updated version.

edited Mar 13 '14 at 13:34

Alex Zavatone

4,106
36
54

answered Feb 19 '14 at 14:49

ohnit

423
3
9

if there isnt one, just open the bundle and edit the info plist and it works again – Daij-Djan Mar 13 '14 at 13:43

score 0 · Answer 5 · answered Jan 31 '16 at 20:36

0

I had deleted unity from my machine. After installing unity the builds worked for me. I was trying to build an app using robovm.

answered Jan 31 '16 at 20:36

dazza5000

7,075
9
44
89

score 0 · Answer 6 · answered Nov 21 '17 at 22:00

0

Maybe it is a bit late, but I had just to restart Xcode after an Xcode update and press the install components button when it showed up. Then my git problems were gone.

answered Nov 21 '17 at 22:00

idunno

71
8

Xcode 5 - Required plug-in not present in DVTPlugInCompatibilityUUIDs?

6 Answers6