While developing a mobile application you can have screens, logic and data running on the mobile device, instead of on the server, to support some use cases as to allow your app to work when offline or to improve its performance. Debug code running on the device side may be useful to track down bugs of the application, troubleshoot plugin issues and check local storage data.
What You Can Debug
You can debug different elements of the code running on the device:
- Debug screens and logic or check local storage: you can debug the logic, screens and local storage of your application by opening the app in the desktop's browser or by opening the application on the device and connect it to the desktop's browser. This last option is useful to debug plugins, but requires the app to be installed on the device;
- Troubleshoot supported mobile plugins on the device without installing the app: use OutSystems Now to check the logs of the application while running in the Apache Cordova shell. Useful to verify if the supported Cordova plugins are working as expected and to check the performance of the app on the mobile device. You must install OutSystems Now before starting to troubleshoot the app;
- Debug app crashing situation and Cordova plugins implementation: you can debug your apps using the mobile platform’s native tools (Android Studio for Android and Xcode for iOS) to troubleshoot situations when your app is crashing, debug a plugin that is not working correctly or check its native code. Before debugging using the native tools you must generate a mobile package with debug/development build type.