1 How Can I Debug a Mendix App?
Developers can debug any deployed instance of a Mendix app running either locally, on premises, or in the cloud. The Desktop Modeler’s built-in debugging tools allow it to connect to and authenticate with an app environment using the app instance’s URL and the credentials provided from within the Mendix Developer Portal.
Once connected, the breakpoints defined within microflows will automatically trigger the events that are trapped by the Desktop Modeler. After triggering, the debugging tool within the Modeler allows you to step through each microflow action, one action at a time, viewing the changing variables along the route.
For more information about how to use the built-in debugging functionality, see How to Debug Microflows in the Mendix documentation.
2 How Can I Debug a Live App Running in the Cloud?
The same debugging tools available when debugging locally are available in the cloud. The debugger can be connected to any Mendix app, whether it runs locally, in the cloud, or on premises.
Read more in How to Debug Microflows Remotely in the Mendix documentation.
3 How Can I Debug My Own Custom Java Code in Mendix?
A microflow can be extended with custom Java actions. To make sure these can also be debugged, the Mendix Runtime and Mendix Service Console have been integrated into Eclipse. If you run into an error in any of the Java actions, you can easily debug them utilizing Eclipse’s debugger.
When you start the debugger in Eclipse, the full Mendix application is started, and the Desktop Modeler console logs all the relevant logging information. This makes the debugging experience seamless and fully integrated.
For further information, see How to Debug Java Actions Remotely in the Mendix documentation.