We will switch tracks. The other side of the equation is debugging your application when it breaks. Nobody is perfect at coding, so understanding the call stack is an important factor in figuring out why your application has just crashed. Both Android and iOS report the call stack slightly differently. So, we shall examine Android first and then finish up with iOS call stack. So, open up your
main-page.js file, and on line three, add the bogus code:
On Android, you get the call stack in two different places. When the application crashes, it normally creates a log in the actual application that you can view and it looks like this:
As you can see, about half way down on the screen, in the ...