As stated in the comments of this issue, setting minifyEnabled false in the debug build is the best practice. By setting this variable in the app module you are disabling the entire proguard build process. It is useful when optimizing the release build, but gives some problems if you are testing and developing.
blue ball: regular breakpoint, active (possibly with a hit count set) empty ball (i.e. white): breakpoint has been disabled (remove checkmark in the breakpoint view, or disable in context menu) diagonal line through breakpoint: all breakpoints have been disabled (button skip all breakpoints in breakpoint view) question mark next to breakpoint: a condition is active … Read more
Opened the network tab in developer tools and pressed F5 to refresh – thanks @Seano666 for your comment on the question
I would build with pdb-only. You will not be able to attach a debugger to the released product, but if you get a crash dump, you can use Visual Studio or WinDBG to examine the stack traces and memory dumps at the time of the crash. If you go with full rather than pdb-only, you’ll … Read more
expr myString = @”Foo” (lldb) help expr Evaluate a C/ObjC/C++ expression in the current program context, using variables currently in scope. This command takes ‘raw’ input (no need to quote stuff). Syntax: expression — Command Options Usage: expression [-f ] [-G ] [-d ] [-u ] — expression [-o] [-d ] [-u ] — expression … Read more
go to Debug menu then Delete All Breakpoints Ctrl+Shift+F9
Specifically, like this in C#: #if (DEBUG) Debug Stuff #endif C# has the following preprocessor directives: #if #else #elif // Else If #endif #define #undef // Undefine #warning // Causes the preprocessor to fire warning #error // Causes the preprocessor to fire a fatal error #line // Lets the preprocessor know where this source line … Read more
update 4.0.0 StackBlitz example update RC.1 Plunker example In the browser console on the top-left (filter symbol) select plunkerPreviewTarget (or launch the demo app in its own window) then enter for example Select a component in the DOM node and execute in the console ng.probe($0); or for IE – thanks to Kris Hollenbeck (see comments) … Read more
It seems that you are mixing object files built with different settings. Try to do a full clean rebuild and check all project file settings to make sure that the _ITERATOR_DEBUG_LEVEL macro is the same (e.g., you are not mixing debug and release built objects).
Foreword The only exception explicitly raised by the decoding code is json.JSONDecodeError, so the exception type does not help diagnose problems. What’s interesting is the associated message. However, it is possible that decoding bytes to text fails, before JSON decoding can be attempted. That is a separate issue beyond the scope of this post. It’s … Read more