View Logs

Filter by IDE
Select the Progress AppBuilder client you are currently using for development.

IDE

When debugging or troubleshooting your app, you can inspect the AppBuilder logs to identify possible issues.

Prerequisites

  • Verify that your preferred AppBuilder client is running and you are logged in.
  • Verify that you have opened the code for your app in AppBuilder.
  • If you want to inspect the log for apps which run in the developer apps, verify that you have installed the latest version of the Platform companion app on your device.

Procedure

In-Browser

  • Inspect the output log in the Output pane.
    By default, the Output pane is collapsed. In the output log, you can track general issues with the AppBuilder services and modules, such as version control, loading modules, synchronization, building the app, deploying on device and others.
  • Inspect the Device Simulator log.
    In the Device Simulator log, you can track debugging events such as console messages.
    1. Launch the device simulator.
    2. Press F12 to launch the debug tools.
    3. In the pop-up window, click Console.
  • Inspect the app log in the Platform companion app.
    1. Run the Platform companion app.
    2. Tap My Apps.
    3. Tap your app.
    4. Tap View Log.
    5. Inspect the log.
      Note that the log does not refresh automatically. Perform a pull-to-refresh gesture to get the latest changes manually.

Windows

  • In the status bar, click Show OutputLog to inspect the output log.
    In the output log, you can track general issues with the AppBuilder services and modules, such as version control, loading modules, synchronization, building the app, deploying on device and others.
  • In the status bar, click Show OutputDevice Simulator to inspect the Device Simulator log.
    In the Device Simulator log, you can track debugging events such as console messages.
  • In the status bar, click Show Output and open the tab with the device name to inspect the Devices log.
    In the Devices log, you can track debugging events such as console messages.
  • Inspect logs stored on your system.
    The classic Windows desktop client stores the output logs for all your sessions as LOG files on your file system. File names for logs from classic Windows desktop client begin with the Graphite prefix.
    1. In the Windows explorer, navigate to %LOCALAPPDATA%\Telerik\BlackDragon\Logs.
    2. Open the LOG file that you want to inspect.
  • Inspect the app log in the Platform companion app.
    1. Run the Platform companion app.
    2. Tap My Apps.
    3. Tap Open for the app whose logs you want to inspect.
      If you see Install instead of Open, you have not installed the Cordova developer app on your device. Install the missing developer app and try again.
    4. Test your app in the Cordova developer app.
    5. Return to the Platform companion app and tap your app.
    6. Tap View Log.
    7. Inspect the log.
      Note that the log does not refresh automatically. To check for new entries in the log, return to the previous page and tap View Log again.

Visual Studio

To inspect the logs available in the extension for Visual Studio, complete the following steps:

  1. To show the Output pane, in the main menu bar, click ViewOutput.
  2. (Optional) To inspect the output log, from the Show output from drop-down menu, select AppBuilder.
    In the output log, you can track general issues with the AppBuilder services and modules, such as version control, loading modules, synchronization and others.
  3. (Optional) To inspect the device simulator log, from the Show output from drop-down menu, select Device Simulator.
    In the Device Simulator log, you can track debugging events such as console messages.
  4. (Optional) To inspect the devices log, from the Show output from drop-down menu, select your device name.
    In the device log, you can track debugging events such as console messages.
  5. (Optional) To inspect logs stored on your system, in Windows explorer, navigate to %LOCALAPPDATA%\Telerik\BlackDragon\Logs and open the LOG file that you want to inspect.
    The extension for Visual Studio stores the output logs for all your sessions as LOG files on your file system. File names for logs from the extension for Visual Studio begin with the VSE prefix.
  6. (Optional) To inspect build logs, from the Show output from drop-down menu, select Build.
    In the Build log, you can track the build progress and status.

If you have connected your project with the cloud, you can also inspect the app log in the Platform companion app by completing the following steps:

  1. Run the Platform companion app.
  2. Tap My Apps.
  3. Tap your app.
  4. Tap View Log.
  5. Inspect the log.
    Note that the log does not refresh automatically. Perform a pull-to-refresh gesture to get the latest changes manually.

CLI

  • Inspect any output messages in the command prompt.
    The command-line interface prints output messages on every operation. In the output log, you can track general issues with the AppBuilder services and modules, such as version control, loading modules, synchronization, building the app, deploying on device and others.
  • Inspect a detailed diagnostic log for the current operation in the command prompt.

    1. Run the following command.

      appbuilder <Command> --log trace
      

      Where <Command> is the command with configured parameters and options that you want to run.

    2. Wait for the operation to complete.
    3. Inspect the log in the command prompt.
  • Inspect the device simulator log, if the device simulator is running.

    1. Run the following command.

      appbuilder simulate
      
    2. If you are running the command-line interface on a Windows system, click Debug.
    3. If you are running the command-line interface on a macOS system, select ToolsDebug Tools.
    4. Click Console and inspect the log.

Next Steps

Continue debugging your app in the device simulator.

See Also

Start a free trial Request a demo
Contact us: +1-888-365-2779
sales@telerik.com
Copyright © 2016-2017, Progress Software Corporation and/or its subsidiaries or affiliates. All rights reserved.