Xcode Command-Slash Shortcut to Comment Only Works Sometimes

XcodeCommentsKeyboard Shortcuts

Xcode Problem Overview


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.

Xcode Solutions


Solution 1 - Xcode

For an Xcode 8, solution is

sudo /usr/libexec/xpccachectl

and restart your computer.

Solution 2 - Xcode

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.

Solution 3 - Xcode

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.

Solution 4 - Xcode

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.

Solution 5 - Xcode

Oscahie's answer actually works for non-beta versions of Xcode as well. Here are the steps to follow, based on Sam's comment:

  1. Close Xcode
  2. In the Application folder, rename Xcode.app (or similar) to Xcode2.app. You might need to type in your password.
  3. Open Xcode, then close it.
  4. Rename Xcode2.app back to what it was before.
  5. (Optional) Spend 5 minutes wondering why this worked.

No need to reboot!

Solution 6 - Xcode

I didn't have to do any of the above. A simple reboot fixed it.

Solution 7 - Xcode

A simple workaround works good for me with following steps:

  1. Comment any line i.e. simply add "//" in front of a line.
  2. Press Command + "/" and it starts working.

It might help someone.

Solution 8 - Xcode

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!

Solution 9 - Xcode

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.

Solution 10 - Xcode

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

Screenshot of Keyboard shortcuts in Mac system preferences

Solution 11 - Xcode

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.

Solution 12 - Xcode

Just quit xcode completely and restart. Worked for xcode 8.2

Solution 13 - Xcode

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.

Solution 14 - Xcode

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

Solution 15 - Xcode

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.

Attributions

All content for this solution is sourced from the original question on Stackoverflow.

The content on this page is licensed under the Attribution-ShareAlike 4.0 International (CC BY-SA 4.0) license.

Content TypeOriginal AuthorOriginal Content on Stackoverflow
QuestionStonz2View Question on Stackoverflow
Solution 1 - XcodeCryingHippoView Answer on Stackoverflow
Solution 2 - XcodeatulkhatriView Answer on Stackoverflow
Solution 3 - XcodeMattView Answer on Stackoverflow
Solution 4 - XcodeOscar HierroView Answer on Stackoverflow
Solution 5 - XcodeKqtrView Answer on Stackoverflow
Solution 6 - Xcodeuser1366265View Answer on Stackoverflow
Solution 7 - XcodeschinjView Answer on Stackoverflow
Solution 8 - XcodeHaroldView Answer on Stackoverflow
Solution 9 - XcodeOhmyView Answer on Stackoverflow
Solution 10 - XcodeChristian SchusterView Answer on Stackoverflow
Solution 11 - XcodeHlungView Answer on Stackoverflow
Solution 12 - XcodeAkul TomarView Answer on Stackoverflow
Solution 13 - XcodeGopal DevraView Answer on Stackoverflow
Solution 14 - Xcodeclaude31View Answer on Stackoverflow
Solution 15 - XcodePreetam JadakarView Answer on Stackoverflow