Joulescope UI Unexpected Error

The Joulescope UI encountered an error,
and it cannot start correctly.

After upgrading to new version I got the following error

Hi @konlog and welcome to the Joulescope Forum! Sorry to hear that you are having issues with the latest UI version. Unfortunately, that image chopped off the error. However, I think that error indicates that the configuration that stores the Joulescope UI state between program invocations is invalid. You can fix this by deleting the existing configuration, which will revert to the defaults.

The process varies based upon your host operating system.

Windows

You need to delete the configuration file:
%LOCALAPPDATA%\joulescope\config\joulescope_ui_config.json

Method 1:

  1. Open Windows file explorer
  2. In the navigation bar, type: %LOCALAPPDATA%\joulescope\config
  3. Select joulescope_ui_config.json
  4. Press delete
  5. Install Joulescope UI 1.0.23 and start the Joulescope UI

Method 2:

  1. Open a command prompt
  2. Type: del %LOCALAPPDATA%\joulescope\config\joulescope_ui_config.json
  3. Close the command prompt
  4. Install Joulescope UI 1.0.23 and start the Joulescope UI

macOS

You need to delete the configuration file:
~/Library/Application\ Support/joulescope/config/joulescope_ui_config.json

Method 1:

  1. Open Finder
  2. Select Go → Library
  3. Select Application Support, joulescope, config
  4. Control-click on joulescope_ui_config.json
  5. Select Move to Trash
  6. Install Joulescope UI 1.0.23 and start the Joulescope UI

Method 2:

  1. Open a terminal
  2. Type: rm ~/Library/Application\ Support/joulescope/config/joulescope_ui_config.json
  3. Close the terminal
  4. Install Joulescope UI 1.0.23 and start the Joulescope UI

Linux

You need to delete the configuration file:
~/joulescope/config/joulescope_ui_config.json


Does this fix the issue for you?

Hi @konlog - I am going to assume that the above fix worked from you since you did not follow up. Starting with Joulescope UI 1.0.28 [download], the UI will be able to report errors like this with much more detail. If this happens again with 1.0.28 or newer, please submit the error.