How to collect logs
Citrix Workspace app for Chrome OS provides timestamps for the logs generated by the user device.
As an end user, to assist with troubleshooting connection issues, logs can be generated on both the user device and the machines providing desktops and applications.
To enable logging on user devices
- On the user device, launch Citrix Workspace app and navigate to the login page.
- Select the button with a settings image in the bottom-right corner.
In the Settings dialog, select Start Logging.
Details of the collected log files are listed in the Settings dialog.
- Select Stop Logging to end the collection of logs on the user device.
- Click the Settings button on the bottom right of the Citrix Workspace app Sign In screen.
- Click the Start Logging button under Account to enable collection of logs.
- The Start Logging button changes to Stop Logging. This change indicates that collection of logs is enabled. Close the Account dialog box.
- Log into the Citrix Workspace app virtual desktop and launch your virtual app session and reproduce the issue to collect logs. Continue to work on the session to reproduce the issue.
- Once the issue is reproduced, close the session.
- Click the Settings button again to open the Account dialog box.
- The Account dialog box shows the list of Log Files captured.
- Moving the mouse on top of any of the Log files shows a small arrow at the right.
- Click the arrow button to download and save the Log file.
- Save all the log files listed under Log files and share it with the administrator or Citrix support engineer.
- Click Stop Logging.
In the case of Kiosk mode, files can be saved to a USB removable device.
- Starting from release version 2205 and later, the console logs are a part of the client logs. Hence, collecting the client logs alone can suffice.
- Open chrome://inspect/#apps page in the Google Chrome browser of your Citrix Workspace app.
- In the Apps tab, click inspect for all Citrix Workspace-related windows: SessionWindow.html, Main.html (and its child nodes).
- For each opened developer tool window, click Console. Then, save the entire log by right-clicking and selecting the Save as option.
USB redirection logs
- Follow the steps in Using Web.config for Chrome OS and enable moreLogs for USB by:
Adding the moreLogs configuration value to chromeAppPreferences in the web.config file on the StoreFront:
- Then, open a new tab in the Google Chrome browser and enter chrome://device-log and share the logs.
File transfer logs
The file transfer logs can be retrieved from both the client and the server.
To retriever file transfer logs from the client:
- Launch a browser.
- Go to the following URL to start logging: <storefronturl>/clients/html5client/src/viewlog.html where <storefronturl> is the FQDN or IP address of the StoreFront server where the store is configured.
For more information on file transfer, see HTML5 and Chrome File Transfer Explained.
Microsoft Teams optimization logs
Microsoft Teams optimization supports the latest shim library version 126.96.36.199.
To know the current shim version that you use:
- Launch the Microsoft Teams application and initiate a call with one of the users.
- Maximize the Microsoft Teams window after the call is established.
- Open the On-screen keyboard inside the session and click Ctrl + Alt + Shift + 1 keys. You can now view the log files under the downloads folder.
- Open the MSTeams_Diagnostics Log <date><time>.txt file and search for the shim version under type_script. Compare the shim version with 188.8.131.52.
- (Optional) If the shim version is not 184.108.40.206, contact your administrator to upgrade to the latest version.
Client logs in kiosk mode
To collect the logs in kiosk mode:
- Connect a removable USB device to your Chromebook.
- Download the log file.
- Save the log file in the attached USB device. The log file is transferred to the USB device.