I just installed a software update that I was prompted for, presumably affecting Xcode. Now when I start Xcode, I am presented with a dialog box which states that Xcode must install the Mobile Device Framework before continuing. When I try to do this, after providing my password, it fails with "An unknown error occurred. See the install log for more details." I do not see anything useful in install.log that identifies the problem. I've tried re-installing multiple times and rebooting to no avail.
I'm currently running Xcode 4.3. Perhaps I need to upgrade to 4.4? Has anyone else run into this problem?
This problem has once again appeared in Xcode 11.1 and is caused by an invalid certificate that expired some day in October 2019.
You can work around the problem by temporarily changing the system date to before the certificate expiration date.
In the case of Xcode 11, set the system date to Oct 3, 2019, run Xcode, then change the date back after the components have installed.
In Xcode version 4.3.1 (4E1019), I suspect that I got the problem after an iTunes update this morning. Found the following somewhere on the web:
Go to Applications folder
Right click Xcode
Click Show Package Contents
Then navigate to Contents/Resources/Packages. Double click on Install MobileDevice.pkg.
Just change the date to October 2019:
I tried installing the required components:
but I had the same issue:
I recommend #Darren answer (https://stackoverflow.com/a/58651694/7602110) but I tried another way, which was uninstalling Xcode and installing it back again, is not the best way to go, because we all know how long that Xcode takes to install, but it also works and was worth sharing.
im resolver that change terminal date for example:
sudo date 103106
The same happened to me after an update to Big Sur version.
A very similar solution as reported here by #cugino worked to me, as follows:
Go to "Applications" folder > Right click Xcode > Click Show Package Contents > Then navigate to Contents/Resources/Packages.
Double click on Install XcodeSystemResources.pkg.
Using cugino's answer above solved it for me. In my case, the certificate used to sign the .pkg file had expired. This may be the reason for anyone experiencing this after February 14, 2015
I am a newbie in iOS development
I was facing same problem while trying to install XCode 6.4 on my 2009 mac pro 13inch with macOS yosemite. I do not know why, just after I changed the system time back to 10th October 2019 according to one of the answers in this thread and click on "try again" button, XCode was finally installed and running!
After this, I changed my system time back to current time (chose the automatic date and time option) and everything works good for me.
Change Time in OS x10.11 or ....
This worked for me:
$ sudo xcode-select --switch /path/to/Xcode.app
$ sudo xcodebuild -runFirstLaunch
Related
I recently updated my XCode to latest(period) 13.3 and working on a project on that, Now when i moved that project to other mac which has MacOS Catalina and has XCode version 12.3.
When i try to open the project it keeps showing me this dialogue
But i found a solution to make it work on lower version XCode which can be useful to other people too, So i am including answer too.
Hope It Helps :)
Just have to follow steps given below
Right Click On Your_Project_Name.xcodeproj and select Show Package Contents from the option menu. { Even if you have .xcworkspace, ignore it for now }
Open project.pbxproj from opened folder.
Change object version to 46 like given below
Hit Command(⌘) + S to save it and close the window.
If you have pods installed on that project then you have to reinstall them again { I guess you already know how to do that or follow setps given below }
Open Terminal
Run Command cd PATH_TO_YOUR_PROJECT_FOLDER, Hit Enter
Run pod install {No need to open podfile as we never made a change to it} and we're done
Go back to project folder and open Your_Project_Name.xcodeproj or Your_Project_Name.xcworkspace
NOTE:
Since It is work around way, we can not run this on newer iOS version simulator on which we want to test code However, we can run the code on physical device which has newer iOS version { which is also tricky part! }
TO RUN THE CODE ON LATEST IOS PHYSICAL DEVICE, FOLLOW BELOW STEPS
Download zip of your desired iOS version to run from the link
Close the XCode App.
Right click on XCode App from Application and select Show Package Contents
Move the downloaded folder to Contents/Developer/Platforms/iPhoneOS.platform/DeviceSupport.
Open the project and run it on physical device
If you get error of Unable to install the Application, click on Details and try to resolve it.
If your error says The code signature version is no longer supported then check out this answer, it solved the error.
Hope It Helps !!!
Why "Add Documentation" is disabled in Xcode 8.2? How can I enable it?
This issue seems to appear randomly for myself as well. The only surefire way I've found to re-enable it is to run
sudo /usr/libexec/xpccachectl
in the terminal and restart my computer.
For the making it enable you need to select code first like following gif and you can add documentation based on selection.
It's ridiculous that it still happens even with Xcode 10.1. And it have a ridiculous solution:
Exit Xcode, then rename Xcode.app to something else like Xcode1.app, then back to Xcode.app. For Appstore version you will be asked for admin password.
I'm having issues with Xcode being quite unreliable when using the keyboard shortcut to comment or uncomment code ⌘+/. I can't seem to find a real pattern as to when it breaks, but it usually happens after building and running my code on the simulator. It will not work again until I edit something in any one of my code files. Even if I switch to another file in the main view, commenting via shortcut does not work. Other keyboard shortcuts, such as indenting ⌘+[ continue to work just fine.
Do other people have this issue, and if so, have you found a solution? I know it seems like a small complaint, but when running and then quickly trying to comment out a block of code to check the effect, it's a bit of an inconvenience.
I am using Xcode 6.1 (6A1052d) on OXS Yosemite 10.10 (14A389) and developing in Objective-C for iOS if that matters.
For an Xcode 8, solution is
sudo /usr/libexec/xpccachectl
and restart your computer.
Hit ⌘+] once and then ⌘+/ will start working again.
You can hit ⌘+[ to undo the indentation effect.
Update:
Please note- This solution was provided prior to Xcode 8 launch so it may not work for everyone. If you are still facing problem, kindly refer to #CryingHippo's answer instead of downvoting.
I have done this numerous times with Xcode 8. Latest being Xcode 10.1 where I would just quit Xcode and go to Applications and rename Xcode to something else, e.g. Xcode 2, launch it, quit again and rename back. It starts working after that. No Mac restart or Terminal commands required.
It still works as of Xcode 10.1. I cannot believe Apple still hasn't fixed it properly.
None of the above solutions worked for me with Xcode 8.0 (final). If you also have Xcode 8.1 beta installed like I do, try this: simply rename /Applications/Xcode-beta.app to something else, then restart Xcode 8. Oddly enough, that did the trick.
Oscahie's answer actually works for non-beta versions of Xcode as well. Here are the steps to follow, based on Sam's comment:
Close Xcode
In the Application folder, rename Xcode.app (or similar) to Xcode2.app. You might need to type in your password.
Open Xcode, then close it.
Rename Xcode2.app back to what it was before.
(Optional) Spend 5 minutes wondering why this worked.
No need to reboot!
I didn't have to do any of the above. A simple reboot fixed it.
A simple workaround works good for me with following steps:
Comment any line i.e. simply add "//" in front of a line.
Press Command + "/" and it starts working.
It might help someone.
In my code I had this sequence:
/*" BLABLA MY COMMENTS */
All the code under this was not "commentable".
Removed the " and it was ok !
Hope it helps!
I just had the same issue after setting up a new Mac with Xcode 10.1 using the German keyboard layout.
The solution was to disable the Keyboard shortcut in system settings for the help menu.
System settings > Keyboard > Shortcuts > App shortcuts.
There was a shortcut for all apps to show the help menu.
If you have that, click the checkbox to disable it
I am using Xcode 8.1 (not beta) and I had the same problem, not able to cmd+\ to comment. Restart Xcode not working for me but RESTART my Mac SOLVED the problem without a need to remove cache.
I had this problem in Xcode 8.0. Even though I already move Xcode 8.1-beta somewhere else (It's at Application/Xcode otherversions/Xcode 8.1-beta.app). I have to delete it to the trash, restart Xcode 8.0, and cmd+/ somehow works again.
Just quit xcode completely and restart. Worked for xcode 8.2
I was also facing this issue, when having multiple Xcode installed.
In which Xcode version you are you facing this problem, to solve this, the Xcode should be in the Application Folder. If it resides in the subfolder than move it to the Application folder directly.
I found a pattern where toggle comments do not work.
In fact, uncomment works, but comment don't, from keyboard as well as from the Editor menu.
This happens in a specific file, suggesting there is something in text that prevents from working.
I tested on XCode 10.1ß and on XCode10.2, on different machines.
Text before this line can be commented, text after cannot (I kept text exactly as is)
let alert = UIAlertController(title: "" /*"Teste texte"*/, message: "Love\nWe'll recommend more for you" /* Entrez des chiffres"*/, preferredStyle: .alert)
It appears that the /* … */ inside the UIAlertController() is the cause.
If I suppress both comments inside, everything works OK.
I filed a bug report. # 49907361
Nothing above worked, even after trying multiple times.
Just reinstalled new xcode using AppStore app, previously I installed xcode after downloading from
developer.apple.com/downloads. that is .xip file
Wait for new update and install.
Another reason may be that xcode isn't in Application directory.
I start by saying that I've installed Mavericks, I was curious to see the new features...
It was better to wait, because (apparently) there are no sensational changes.
Anyway, I'm trying to submit my app to the app store, but after a real hard fight with the code-signing, I have ended up with this message:
"This bundle is invalid. Apple is not currently accepting applications built with this version of the OS."
....From what I read, the only solution seems to uninstall Mavericks and go back to Mountain Lion, but I will be happy if someone else has got a alternative fix.
After some research on Internet I've found a fix for this problem.
1) Open "App Store" and leave it for now.
2) press cmd+shift+g on your desktop and go to /system/library/coreservices/
2) Copy SystemVersion.plist to your desktop, and duplicate the file
3) Open the file with the right name on your desktop, not the copy, and replace the old part with this:
<key>ProductBuildVersion</key>
<string>12E55</string>
<key>ProductCopyright</key>
<string>1983-2013 Apple Inc.</string>
<key>ProductName</key>
<string>Mac OS X</string>
<key>ProductUserVisibleVersion</key>
<string>10.8.4</string>
<key>ProductVersion</key>
<string>10.8.4</string>
4) Now copy this edited file to /system/library/coreservices, and go to "App store" application.
5) Download Xcode 4.6.3, now you can because your OsX is detected as Mountain Lion.
6) Once the download its finish, and Xcode installed, reboot.
7) Open your project in xcode 5 beta, if you have some .xib files, go in the file inspector, document versioning, and change development version to 4.6 instead of 5. Do this for each .xib, then close xcode 5
8) Open Xcode 4.6.3 and reopen your project. Check in the build settings that 10.9 is not present anywhere. Replace it with 10.8 or whatever you need.
9) Make clean, Build for archiving, Archive ... Cross your finger!
10) Your project should be validated now.
11) Once you uploaded your app, rename the SystemVersion.plist (copy) on your desktop, and copy it back to /system/library/coreservices. You don't need to reboot.
It's kinda a hack, but if you don't want to reinstall everything, it's the only way to go.
P.s: after replacing SystemVersion.plist, you will notice strange behaviors in the Os, like safari that isn't working and so on, that's why I suggested to duplicate the plist file, before changing the os version. Anyway if you can still use terminal and "vi" to restore everything, if for some reason you didn't copy the original.
Hope this will help someone. I've lost a day figuring out a solution ;)
Same problem with build 13A3017 on Mavericks
Switched it to 13A603 and it worked.
It's quicker to use this command in terminal and just make a note of the original build number to switch it back afterwards.
sudo nano /System/Library/CoreServices/SystemVersion.plist
but should probably make a copy of the file first just in case
I got this problem while I was using Mavericks 10.9.1 (build 13B40) and Xcode 5.1 dp. I finally solve the problem by:
Use Xcode 5.0.2 instead of Xcode 5.1 dp.
Go to /system/library/coreservices/ and modify the SystemVersion.plist using the copy/paste as #Benz 's answer. Thanks to #Benz
After copying and backing the SystemVersion.plist, modify the content as following:
mod ProductBuildVersion to 13A603, which is the build number of Mavericks 10.9.0 GM.
mod ProductUserVisibleVersion and ProductVersion to 10.9.0
Replace the SystemVersion.plist using the one you've modified.
Restart the Xcode.
Rebuild and achieve the app.
Submit.
Succeed!!!
Restore the SystemVersion.plist using the original file you've backed.
If you don't want to mass with the SystemVersion.plist, here is another way to get through it on 10.10:
After you made the archive, you can modify the .app bundle and .plist in the archive's root to match a valid accepting version. Then use the Xcode to submit it. No need to mass with the code signing or Application Loader.
If you want a simple solution and don't mind to pay for it, I've created a tool to do it with ease: https://vox.vg/xcarchiver/
I have tried to install Xcode 3.2.x on Lion using two methods below, but both failed.
Did anyone succeed with that two methods?
Method 1:
right click on "Xcode and iOS SDK.mpkg" and choose show package content;
modify the Contents/iPhoneSDKSL.dist to replace "10.7" with "10.8" in it;
install.
Method 2:
open the terminal;
export COMMAND_LINE_INSTALL=1;
open "/Volumes/Xcode and iOS SDK/Xcode and iOS SDK.mpkg"
uncheck all but the first one that include sdk and ide to install.
Besides, I also tried to use both two methods together, but failed again.
Any help?
Actually I'm not sure if you can do this. Because Xcode 3 it's too old for Lion. But there might be some kind of hack.
Try to set system clock back in time. It failed for me because of old certificate. I used 6th of May 2011