Xcode Command-Slash Shortcut to Comment Only Works

Question

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.

Answer 1

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!

Answer 2

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

Answer 3

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.

Answer 4

Just quit xcode completely and restart. Worked for xcode 8.2

Answer 5

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.

Answer 6

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.