Xcode 13: Active breakpoint turns to an outline when app is run.

A clarifying note (I hope); when I wrote "Breakpoints work as expected on an app started in Xcode 13.1." I meant apps that I started development on Xcode 13.1. Breakpoint work normally in this case; it's only debugging apps written on earlier versions of Xcode that give me this problem.

I'm working on several projects which were created with Xcode 12.x (or older), but have never experienced the behavior as you described. Can you share the screen shots?

I think I can add screenshots only by answering (I'm no expert at these forums), so here goes: Screenshot of the code before starting the app in a simulator:

Once the app is running in the simulator:

Changed my comment to an answer

I just saw this happening too, then I realized that the code wasn't being called. Meaning once the app compiled and the compiler realized it was not possible for the breakpoint to ever hit it would turn to the dotted outline. At least that was the case for me.

I have this problem too, but the code in question is definitely supposed to hit. If it didn't, then it wouldn't work. But the breakpoint is being turned into a dotted line and I am unable to debug.

I'm also having a same issue. I have not found any solution to this issue for a month. Please let me know if there are any updates.

In my case cleaning the build folder and erasing derived data fixed the problem

What is the solution Apple.. It is killing me

I'm the original poster on this question. I wish I could give you an answer, but I cannot. The situation I originally described corrected itself; I can't tell you what was wrong or what fixed it. I have seen the same behavior a couple times since, but again, it seemed to resolve itself. Apple tech support was of no help. I wish you luck in finding a solution and please post it if you find one.

Make sure your source file compile into your running target. And symbol name is correct.

Check target -> build Phases -> Compile Sources ...

I’m having the same problem in a C program. I just tried compiling for testing iso running and am now able to run my program with functioning breakpoints. I’m not technically sophisticated enough to understand the implications or how to use this information to resolve the issue when compiling for running though. FWIW.

I encountered the same problem, but luckily was able to hit a different breakpoint at a later point in the same flow. I moused over the outlined breakpoint and saw the following tool tip:

Xcode won't pause at this breakpoint because it has not been resolved.

Resolving it requires that:

• The line at the breakpoint is compiled.
• The compiler generates debug information that is not stripped out (check the Build Settings).
• The library for the breakpoint is loaded.

I was stuck with this issue for a year - I had scoured the forums and the rest of the internet for any clues and just recently finally was able to get past this issue. The solution for me was to simply reclone my repository in a new directory. Once I created a new local repo at a different path the debugger magically worked again! I hope this helps someone in the future!

Rebooting the machine fixed the problem for my case