You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If you have set a breakpoint in a code which is executed on module execution (e.g. in an immediately executing function or some "global code") the breakpoint setting message is likely to be sent after the code is executed, so the debugger doesn't break the first time. If the code is executed again after a certain amount of time the debugger breaks. Inserting a debugger; statement before the breakpoint will delay the execution of the code and the breakpoint setting message is likely to be already sent, so the debugger will break on the breakpoint.
If you have set a breakpoint in a code which is executed on module execution (e.g. in an immediately executing function or some "global code") the breakpoint setting message is likely to be sent after the code is executed, so the debugger doesn't break the first time. If the code is executed again after a certain amount of time the debugger breaks. Inserting a debugger; statement before the breakpoint will delay the execution of the code and the breakpoint setting message is likely to be already sent, so the debugger will break on the breakpoint.
Related to: https://github.com/NativeScript/Neudesic/issues/2
The text was updated successfully, but these errors were encountered: