In reality, the_main.js_file was incorrectly built or is missing altogether. This can result in a “white screen of death,” as it commonly known. There are times when the build scripts are running, and something causes them to run again before they finish their first build of cycle. This is very useful most of the time, but the Ionic build process takes a moment or two to run.
Now, one of the features of ionic serveis that it will watch your source files and trigger a rebuild when it sees that one of the files has been updated. One of the simplest steps you can take as you start to debug your application is to ensure that all the files are saved.Ī lot of your development will be in your local browser and using $ ionic serveto run your application. Then as you test your application, you are scratching your head wondering why something is not working correctly. It is easy to forget to save one or more of the files before you attempt your next build. Often when working on a particular screen, you may have its HTML file open to adjust some markup, the SCSS open to modify the visual look, and the TypeScript file open as you edit the component’s code. The most common one that we have found is that it does not recognize that there may be unsaved files in your project when you attempt to build your application.
#Ionic ios emulator mac android#
This gives you the ability to see the various build events, and if an issue occurred.Ĭoming back to the fact that we are not working with complete IDE (like Xcode or Android Studio), some of the build debugging tools are not there to assist us. One recommendation we have is to have your console window actually show more than a few lines of output. You may find you missed a comma in an object or some equally hard to spot a typo in your code. If your application isn’t launching for some reason, the first place to start is to look at the build output to your console. However, more than once have we seen error messages get written to this window, only to have them quickly scroll out of view. If you are like most, this is probably just a small window, tucked in the corner of your screen. As you might have noticed, when compiling your Ionic application, a lot of messages are written to your console’s window. The next element you can use in resolving issues is the compiler output itself. Now, your IDE won’t be perfect in spotting everything while you are editing your code. Spotting these simple mistakes can save a lot of questioning on why your application is having issues. There are times when a reference is incorrectly updated when refactoring or a path to a module is off by a sub folder. If your IDE is complaining about a variable or a function, that is usually a good sign that something is amiss. With Ionic now being developed in TypeScript, this is actually our first line of defense in writing a working application. But even before turning to those solutions, there are some other first steps we can take. Since Ionic is built atop web technologies, often the best place to start debugging is with our browser. Each one of the phases offers different levels of insight into your application.
#Ionic ios emulator mac how to#
Let’s learn how to use some of the debugging tools.ĭebugging your Ionic application can be broken down into three distinct phases:browser level, emulator debugging, and on-device debugging. This can be a challenge for some developers who are used to having a complete ecosystem to work within. Since Ionic is built atop a collection of technologies, this means that debugging your application may not always be straightforward. In this chapter, we will look at various solutions and tools you can use to help you resolve possible issues that may arise. There will come a time when you need to debug your Ionic application. Chapter 10.Debugging and Testing YourIonic Application
0 kommentar(er)
