Runtime Debugging

The runtime Debugging facility allows you to step through a Script line by line and also to check the contents of variables as you move through the Script to help diagnose and identify problems.

 

Runtime debugging is controlled via two options – one which is set within the app's Project in App Studio and the other within the Digitise Apps Client itself.

In order to be able to use the facility on your devices, you first need to enable it within App Studio, and then a separate option within the Digitise Apps Client is used to stop and start debugging on the device itself. The facility is enabled/disabled on an individual app basis.

    • Debugging mode requires the app to be running in portrait mode.

    • Runtime debugging is not available within Standalone Apps.

 

To use runtime debugging:

Load App Studio and open the Project for the Digitise app experiencing problems.

Display the Project Properties, e.g. by right-clicking on white space in the Forms or Data Sources Panes and choosing Project Properties. Set the Debug Level Property to Diagnostic (high). Ignore the Diagnostic (low) setting as this option is no longer used.

You then need to republish the app and download the new version to a mobile device. If you are debugging a live app, before you download your diagnostic version you may want to configure App Server to only download the app to the device(s) on which you want to run it, to prevent all users getting the diagnostic version.

Return to the Client's Applications list, if not already on it and then follow the relevant instructions below for your Platform type to turn debugging on:

 

Once debugging is enabled, run the required app.

Each time a Script is encountered in the app, before it is run you will be prompted to enter debug mode. Choose Yes to enter debug mode or No to continue running the Script as normal. If you choose No to debugging a Script, you will not be prompted to debug that Script again, until you reload the app.

If you select Yes, the Digitise Apps Client displays a debug screen showing the Script at the top half of the screen and variables in the bottom half of the screen.

To debug your Script:

 

When you reach the end of a Script or after breaking out, you can continue using the app until another Script is run, at which point you will be prompted to debug that Script.

 

When you have finished debugging the app, return to the Client's Home screen and reset the debug option (Debug Scripts or Debugging) back to OFF or deselected (depending upon your device type) within Settings. You may also want to turn debugging off within the Project Properties and republish your app.