I've been using breakpoints in Devtools for a long time, and have had little issue. Lately I've experienced breakpoints not sticking after refresh or when I refresh only one of the breakpoints set will persist. Or sometimes the breakpoint will hit, but the breakpoint will have been removed.
Has anyone been experiencing this or have an idea what might be going on?
Related
I'm debugging a react application using VS Code debugger for Edge (The newer Chromium edition, I used to use Chrome, AFAIR there was the same problem). When I reload a page, the "paused in debugger" label appears a couple of times, then disappears. It doesn't bother me too much, but the problem is it always opens Sources panel and because of that on every reload I have to open Console manually which is very annoying.
I'm absolutely sure I have no breakpoints on, the Breakpoints panel in Edge is empty, the Breakpoints panel in VS Code only contains my breakpoints and the problem persists if I disable all of them. I also have Uncaught exceptions breakpoint turned on, but disabling it doesn't help. Sources panel opens some React internal file, namely injectGlobalHook.js. Also sometimes after reloading a page I open VS Code to find that it opened a tab with react-dom.development.js for some reason. Is it supposed to work like this? And is it possible to make Console tab open on reload, because it's impossible to work like this
Since FF 67 I cannot use breakpoints to debug my javascript on webpages coming from localhost. All breakpoints are completly greyed out so that it is not possible to set any.
I have tried all things in this post
Brekapoints are not deactivated by the deactivate breakpotins button.
I tried to clear the prefs.js file
I also tried the checkboxes for pause on exception
and the checkboxes in the preferences for the dev tools.
Any idea?
I am also running into this issue. I found a fix online but it doesn't always work. Close the debugger window, refresh the page and open the debugger window. You should be able to set the breakpoints now. If you refresh while the debugger window is open, you won't be able to set the breakpoints at all.
Doesn't always work, but I was able to test some js code last night
I put a breakpoint using the debugger in firefox. On refresh, the breakpoints go away and the webpage loads completely. What may be the issue? I was able to successfully preserve breakpoint in chrome.
When I call stop on my AVAudioRecorder instance XCode stops at a breakpoint. However, no exception comes up and I don't have my own breakpoint set there. I do have an "All Exceptions" breakpoint setup.
I hit continue and the app runs fine - no message in the console.
What's going on?
It is the All Exceptions breakpoint. AV Foundation is throwing an exception and also catching it, so no harm, no foul (which is why the app can resume without a problem) - but you are set to break when that happens, so you do. When the app runs for real (independent of Xcode) no one will know; it's just Xcode and your All Exceptions breakpoint that brings it to the surface.
AV Foundation is full of places like this. I regard it as a bug, but not enough to care very much. I just turn off the breakpoint when working with AV Foundation; otherwise we'd always be stopping...
Try 'step in' at method declaration in your code. This should take you to the definition of method being called, and you can 'step over' from there. Hope this may help you.
I set a breakpoint but when I run my program it looks like it disables itself. Any ideas what's going on? The breakpoint arrow is dark blue before I run the program, and upon execution changes to light blue.
Breakpoints in Xcode can be fickle...most of the gotchas are detailed in this SO thread:
Why Aren't My Breakpoints Working in Xcode