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

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 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

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

In my case of Xcode 7, remove all Xcode plugins fixed my issue.
rm -rf ~/Library/Application\ Support/Developer/Shared/Xcode/Plug-ins/*

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.

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

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.

Related

How to change build system information path on Xcode?

I got those 4 errors when I open my Xcode project.
/Users/khcw1007/Manao-iOS/manao/Pods/Pods/Target Support Files/Pods-manao/Pods-manao.debug.xcconfig
I've 2 'Pods' in the path of xcode but in reality I've only one, I think that's my error come from here. Where can I edit the path to fix it ? I can't build my project in Swift.
Ok, fixed. I just uninstall and install Xcode again.

Xcode 4.5 building error: Malformed Object

I'm trying to build a project with Xcode 4.5.1, created with Xcode 4.4, but I'm getting following error:
codesign_allocate: for architecture armv7 object:
/Users/myUsername/Library/Developer/Xcode/DerivedData/MyAPP-araevdowzmmoupfieakjpjmpsmhq/Build/Products/Debug-iphoneos/MyAPP.app/MyAPP
malformed object (unknown load command 36)
/Users/myUsername/Library/Developer/Xcode/DerivedData
Can somebody help me please?
Thank you!
Update:
I still have this problem but only when compiling for iOS Device, not for the simulators. I'm not able to create an archive.
PLESE HELP ME!
SOLVED
The problem was due to a "Run Script" in Build Phases I was forgotten....and that pointed to the old path /Developer
Delete your derived data, perform a clean build, and try again.
To delete your derived data, go to Organizer->Projects, and select `Delete...'
To do a clean build, select Project in Xcode, and select "Clean"
Update: Validating your project settings may help here also. Go to your Project file in Xcode and select it.
Update 2: Something seems to be interfering with codesign, causing it to use an incorrect loading command. Maybe your old version of Xcode (4.4) left some artifacts behind, which is causing an old version of codesign to be run. I'd suggest uninstalling any instances of Xcode you have, make sure they're all gone, then re-install the latest version.
Update 3: I'm at a loss, I've no idea what's going on. My last suggestion is to create a new Xcode project, and migrate your stuff over; something may have interfered with your build settings, which might be a case of looking for a needle in a haystack. Make sure you have the latest Xcode and OS X.

Cordova-Based application not and option for newProject

I made the command line helloworld project and it worked. When I try to build from XCode the option to build a "Cordova-Based" application is not there. This picture is what it supposed to show. I don't have the icon. I went through install like the wiki says, Xcode was closed, then I tried the helloworld, success:), and the New Project Cordova-Based... crap, really...
What I should see
and what I do see.
this option was deleted in Cordova 2.xx
you must use the command lines
http://docs.phonegap.com/en/edge/guide_command-line_index.md.html#Command-Line%20Usage
I ran the 1.9 installer and it showed up in Xcode.

Xcode Internal Error upon building

I'm having a very annoying problem with my xcode that I desperately need help with.
Every time I build (or clean) an app, Xcode errors with:
Internal Error: File:
/SourceCache/DevToolsBase/DevToolsBase-1763/pbxcore/Infrastructure/XCWorkQueueOperation.m Line: 895 Object: <XCWorkQueueOperation:0x204e8f820>
Method: runOperation
Assertion failed: commandInvocations[slotIdx] == nil
And it presents me with the option to Quit Xcode or continue.
There seems to be absolutely nothing on Google about this error! And I am completely stuck. I have reinstalled Xcode and all. Rebooting does no good.
Does ANYONE have any idea how to fix this error?
Xcoder version: 3.2.5 on 64-bit OSX 10.6.4
Cheers,
Brett
Try this: "Rebuild Code Sense Index" button in the "General" tab for the inspector for the project. (from http://forum.soft32.com/mac/XCode-project-problem-ftopict47829.html)
Also see the following:
https://lists.apple.com/archives/xcode-users/2008/Feb/msg00550.html
You can allways upgrade to the GM of XCode 4, if everything else fails.
I reinstalled xcode and it went away
If the problem persists after a full reinstall of xcode, your user settings are probably corrupt.
Delete them from a terminal prompt:
rm -rf ~/Library/Application Support/Developer/Shared/Xcode/

iPhone Codesign object file format invalid or unsuitable

I accidentally deleted my target in xcode.
so i created a new one with the exact same name. in the target settings i again selected the proper codesigning identity
but now i can't compile for the device anymore. as soon as i want to build, i get:
CodeSign build/Release-iphoneos/myApp.app
....somestuff....
/Volumes/XCodeProj/myApp/build/Release-iphoneos/myApp.app: object file format invalid or unsuitable
Connad /usr/bin/codesign failed with exit code 1
I already tried to clean targets.
what could cause this problem and how to solve it?
May also be an issue with your install. Symlinking to the latest codesign_allocate cleared up the issue in my case:
sudo mv /usr/bin/codesign_allocate /usr/bin/codesign_allocate_old
sudo ln -s /Developer/Platforms/iPhoneOS.platform/Developer/usr/bin/codesign_allocate /usr/bin
In Mountain Lion, you can try to run this before codesign:
export CODESIGN_ALLOCATE="/Applications/Xcode.app/Contents/Developer/usr/bin/codesign_allocate"
Make sure the 'Executable Name' (CFBundleExecutable) entry in your target's info.plist matches the 'Product Name' specified in your target settings.
I had this issue when I was trying to codesign from the terminal. I had just installed Xcode 4.4 after uninstalling Xcode 3.0. Took a look at the Downloads in Xcode preferences and noticed that the Command Line Tools had not been installed. My issue was fixed after I installed this. I'm guessing the problem is more complex given the solutions here, but this might be something that future users want to check before they have to start diving deeper.
For me, this was occurring after upgrading to XCode 4.5.
The solution was simply to go to Preferences / Downloads and install the latest Command Line Tools.
I had the same problem and tried all sorts of build settings GCC4.0, search paths etc etc. It turned out to be nothing to do with the build settings in my case the problem was I put a dot in the target name i.e. I was targeting v3.0 SDK so I called the target Granade3.0.
I started a brand new project named "Grenade3zero", imported the sources from the original, fixed the appdelegate name to match the project name etc. build and go and it loaded first time onto the device and the simulator was also fine when I checked it. Looks like some characters are illegal in target names!
Thought I'd add my solution to this problem too... I've been struggling for a couple of weeks with this problem... having checked ALL the solutions above and changing more.
My solution was in the target build settings.
I had put in two options, armv6 and armv7. I changed this back to one single entry of normal and it built!
emcmanus answer worked for me but since Xcode 4.3 is now installed in the Applications folder and I removed the old /Developer folder, I had to change the path to codesign_allocate:
sudo mv /usr/bin/codesign_allocate /usr/bin/codesign_allocate_old
sudo ln -s /Applications/Xcode.app/Contents/Developer/Platforms/iPhoneOS.platform/Developer/usr/bin/codesign_allocate /usr/bin
I tried all the above to no avail. What worked for me was to add the following to my build script:
export
CODESIGN_ALLOCATE="/Applications/Xcode.app/Contents/Developer/usr/bin/codesign_allocate"
I came across this post while researching my problem:
http://mobiledevelopertips.com/mac-osx/code-signing-error-object-file-format-unrecognized-invalid-or-unsuitable.html
For Mountain Lion before starting signing process Please run below command as first command.
For Xcode 4.x:
export CODESIGN_ALLOCATE="/Applications/Xcode.app/Contents/Developer/usr/bin/codesign_allocate"
For XCode 5:
export CODESIGN_ALLOCATE="/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/codesign_allocate"
Faced a similar issue in Jenkins running on Mountain Lion and Xcode 5.x.x without any command line utilities.
since the command line utilities are now bundled with Xcode 5.1.x
the following worked
sudo ln -s /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/codesign_allocate /usr/bin/
Go to 'Build Settings'
Go to 'Build Options' tab
Inside of the build options tab go find 'Debug Information Format' and change it's value from 'DWARF' to 'DWARF with dSYM File'. Should be in the dropdown.
It should work for you guys.
If your app has special characters in the Product Name in the target build settings, remove them.
For example, rename "Mat's app" to "Mats app" and it will build. You can of course have special characters in the display name.
I also had the same problem, and the cause was that my app target was linked to a static library and didn't provide its own source files (all sources were in the library and the app target only provided resources). Once I moved out one of the sources from the library to the app target, it fixed the code sign error.
I think that it was cause by one of Xcode DP(developer preview).
It could change default Xcode.app Path to Xcode DP.
So, U can check Xcode path by xcode-select --print-path
If U got some wrong directory then U could change path by xcode-select --switch
check this thread.
change xcrun developer path
It is better to use xcrun to locate the correct version of codesign_allocate as it can be different depending on whether it is an OS X binary or iOS.
This also allows Apple to change the location of various tools without breaking your script.
Use something like:
export CODESIGN_ALLOCATE=$(xcrun --sdk iphoneos --find codesign_allocate)
I would get the error when trying to sign my OS/X (not iOS) application with a digital certificate my company purchased from a root Certification Authority different from Apple. The problem would occur whenever I downloaded the certificate via Safari. Downloading the certificate using Firefox helped me get rid of the error.