I have a problem with the latest version of Aptana (3.2) on MacOS Lion. Very often, when I copy-paste a bit of code (using cmd+C,cmd+V), it opens callback.php, and my code is pasted in it, which is not very convenient.
Do I do something wrong? Is it Mac version only? Is there some key hidden somewhere?
Thanks for your help!
Related
The quick help feature is working just fine when I open an Xcode project, however when opening a file (e.g. abc.swift) that's not in an open project, the documentation does not appear.
Here is an example:
Install the version of the Command Line Tools for your Xcode
`Xcode menu -> Open developer tools -> More Developer Tools
Restart Xcode. It helped me to see Quick Help again and also fixed git crash.
The below code worked for me. Run the following command from Terminal, then relaunch Xcode.
defaults delete com.apple.dt.Xcode IDEIndexDisable
As an occasional user of XCode, what I still needed to do was download the documentation, which was not installed with the XCode install and/or did not carry over from a previous version of XCode.
From the Preferences dialog, click the Components tab, click on Documentation, and then click the download button for Guides and Sample Code.
Probably obvious for regular users of XCode, but I thought I would write it out for anyone else having this problem, since this was at the top of the Google search.
This is what worked for me. I closed Xcode and then deleted ~/Library/Caches/com.apple.dt.Xcode.
Then I reopened Xcode and checked. It worked after that. I'm currently on Xcode 10.2.1.
It's worked for me, just move the Xcode.app into Applications folder if not exist over here ;)
When I try to open the Swift Guided Tour playground from Apple's e-Book, it says "the document can't be opened because it is from a newer version of Xcode. As far as I can tell, I'm using the newest non-Beta version, and I'm not working with Swift 2.0 yet, still learning the first version. Have all the playgrounds been updated to work with Xcode 7 Beta or something? I'm using Xcode 6.3.2, just in case that isn't actually the newest version.
I got the same issue with xcode 6.3.2.
I got the issue when I downloaded it via ibook link. Once I downloaded it via we, it worked.
https://developer.apple.com/library/ios/documentation/Swift/Conceptual/Swift_Programming_Language/GuidedTour.html#//apple_ref/doc/uid/TP40014097-CH2-ID1
My previous version was playground version='1.0' and the new one also same. But it includes lots of new libraries.
I got that problem too, and finally i open it OK, that just problem with where you download your .playground file:
#Xcelleratr Download your file here:
https://developer.apple.com/library/mac/documentation/Swift/Conceptual/Swift_Programming_Language/GuidedTour.html
It will be OK my friend :)
works for Xcode version:
Version 6.3.2 (6D2105)
Version 7.0 beta (7A120f)
Im guessing it was corrupted could check it by:
Right clicking on the playground file > show package contents > open contents.xcplayground in a text editor like sublime and look for playground version='3.0' near the top
If this is any higher it will pop up with the error you seen.
Just in case someone stumbled upon this problem, here is what happened to me:
Download from guided tour page.
Save it with .zip extension instead of .playground, as seen in this picture:
Double click the downloaded file, it will unzip it and you'll get your actual GuidedTour.playground file.
So if you have a playground file and it only opens xcode and not a guided playground, right click the playground fle and show package contents, then go to contents.xcplayground and rightclick and open with text editor.
I had to change this line...
display-mode='raw'>
to ....
display-mode='rendered'>
then save and when you go back and open the playground it should be ok now.
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