Skip to main content





Debugging and troubleshooting mobile and reactive web apps

  • Edit
    Collaborate with us
    Edit this page on GitHub
  • OutSystems provides rich capabilities to develop Mobile Applications and Reactive Web applications. These two application types each have a few unique characteristics, but they also share a common modern technology stack and development model.

    Applications consist on a combination of client-side code and server-side code, which are both key to a great user experience, but can also make investigating and correcting unexpected behavior a bit more involved in certain scenarios.

    The OutSystems platform comes with a very powerful debugger (integrated with Service Studio) and detailed, configurable built-in logging right out of the box. Application logs are accessible via the monitoring section of Service Center.

    These Tools, combined with the Developer Tools offered by modern browsers like Chrome and Safari, provide an excellent starting point for applications troubleshooting and debugging.

    Ample documentation on how to take advantage of this Toolset is available in the Troubleshooting Applications and Monitor and Troubleshoot (Note that the monitoring capabilities of LifeTime aren't available for Reactive and Mobile Apps) sections of the public platform documentation.

    Beyond this standard Toolkit, there's the possibility to add additional Tools into the mix to address more complex analysis needs. This section describes some of these Tools and related advanced troubleshooting and debugging techniques.

    This section's articles address the following topics:

    Also, along the way, learn how the similarities of Mobile and Reactive Web applications allows you to share most of tools and techniques, and where differences between the two may require an application type-specific approach.

    • Was this article helpful?