Skip to main content

August 26, 2026

Collecting Logs and Troubleshooting on Omnissa Workspace ONE Web

Using debugging logs, you can troubleshoot issues related to network, rendering, and get additional information on the errors for Workspace ONE Web.

Enable Debug Logs on Web

To enable debug on Web, configure the following settings.

1. Configuration on UEM Console

  1. Enable Debug.
SettingsNavigation
Default SDK settingsSettings > Apps > Settings and Policies > Settings > Logging (ENABLED) > Logging Level. Select Debug from the drop-down.
Custom SDK profileResources > Profiles & Baselines > SDK profiles > Open > Logging > Configure > select Enable Logging check box > Logging Level. Select Debug from the drop-down.
  1. Ensure to remove any previous logs on UEM Console.

    1. Navigate to Devices > List View.
    2. Open the impacted device details.
    3. Navigate to More > Attachments > Documents tab and click X to delete any existing AppLogs if available.

2. Configuration on the Device

  1. On the device, ensure to clear all the Web app data.
  2. Launch Web and navigate to More > Settings > Support > Enable Diagnostic Logging.
  3. Ensure that you do not close the Web app.
  4. Return to the Web app Home screen.

3. Collect the Diagnostics Logs

  1. Enable Debug Logs on Web.
  2. Reproduce the issue.
  3. On Web, go to More > Settings > Support.
  4. Tap Send logs to Administrator.
  5. On UEM Console, navigate to the respective Device details page > More > Attachments > Documents.
  6. Tap Get all log files (.zip file).

Chrome Debugger and other DevTools logs on Android

  1. Discover the Android device.

  2. Enable Debug Logs on Web.

  3. Open the Developer Options screen on your Android device.

  4. Select the Enable USB Debugging check box.

  5. On your development machine, open Chrome.

  6. Go to chrome://inspect#devices.

  7. Ensure that the Discover USB devices check box is selected.

    Enable the Discover USB devices checkbox

  8. Connect your Android device directly to your development machine using a USB cable. In this case, accept the debugging session prompt on your device's screen.

    • If you are connecting your device for the first time, the device will show as "Offline" and "Pending authentication".

      Web offline device

    • If you see the model name of your Android device, DevTools has successfully established the connection to your device.

      Web Model name displayed on Anroid device

    • If you do not see the device name as mentioned, check if Enable USB Debugging check box is selected on Developer Options screen. Additionally, plug-in the device to another USB port on your development machine and check the quality of the connecting cable.
  9. Navigate to the webpage which needs to be inspected and click inspect to open the DevTools window.

    Inspect option on Web Android

  10. Collect the logs for any URLs that you want to troubleshoot.

Safari Web Inspection other DevTools logs on iOS

  1. Discover your iOS device
  2. Enable Debug Logs on Web.
  3. Go to Privacy & Security settings on your iOS device and turn on the Developer Mode toggle.
  4. Restart the iOS device.
  5. Launch the Web app and ensure that the Web Diagnostic Logging toggle is turned on.
  6. Connect your iOS device directly to your development machine using a required cable.
  7. On your development machine, open Safari (Desktop Browser).
  8. Go to Settings > Advanced tab and select the Show features for Web developers check box.

    show features for web dev checkbox


    The connected device will be available on the Develop menu on Safari Desktop browser.

    connected device

  9. Click on the URL to open the Safari Developer tool (Web Inspector tool) and debug the corresponding webpage.
    Note: If you are connecting your device for the first time, the development machine will prompt for permission to allow/access the connected iOS device.

    If you do not see the device name as illustrated, ensure that the Developer Mode is enabled. Alternately, plug-in the device to another port on your development machine and check the quality of connecting cable as well.

  10. Collect the logs for any URLs that you want to troubleshoot.

Was this page helpful?

Provide feedback for this topic

Was this topic helpful?

Please do not include any personal or confidential information.

Generating link…