About macOS Client 

Supported Operating Systems 

The client is available for all macOS devices that are running macOS 10.14 or higher: 

OS Name 

OS Number 

Supported 

Monterey 

12 

No 

Big Sur 

11 

Yes 

Catalina 

10.15 

Yes 

Mojave 

10.14 

Yes 

High Sierra 

10.13 

No 

 

At the time of release macOS 12 (Monterey) has not been released, a service release will be available in Autumn 2021 adding support for this OS. 

 

Supported Architectures 

The Senso macOS client only support x84_x64 architectures, it does NOT support ARM (Apple Silicone eg M1). 

ARM architectures will be supported by future versions of this software 

 

Application Directories 

Install Directory 

This directory contains the application and any configuration files necessary for the application to operate correctly. 

 

The application is installed in the following directory: 

/Library/Renato Software/Senso Client/ 

 

Collateral Directory 

This directory contains files generated by the client such as the log files and application database 

 

The application collateral folder is located in the following directory: 

/Library/Application Support/Renato Software/Senso Client/ 

 

Menu Bar 

The only UI for this application Is a system tray menu bar. It can be accessed by clicking on the senso icon in the system tray. 

 

The menu features an about menu, status of the client and the current version number. 

About Menu 

This menu displays the current version and specific build of the client. Pressing Ok will dismiss this page. 

Graphical user interface, application 
Description automatically generated 

 

Client Status 

The menu bar displays the current status of the client, the following states are available: 

State 

Description 

Disconnected 

The initial state of the client when it starts up 

Unlicensed 

The app could not establish a valid authorization token to communicate further with the Senso API, this occurs for the following reasons: 

  • Could not find config.json 

  • config.json is missing license details 

  • Details in config.json are incorrect 

  • Client app cannot talk to the Senso API 

Requires Permissions 

The app must be granted OS level permissions before it can function correctly. More can be read about which permissions are required and how to grant them in our article about permissions for the macOS client. 

 

If the app detects any permissions are not granted, it will not continue to startup. 

Initializing 

The app has passed all of its start-up checks (license, permissions) and is initializing modules and getting ready to connect to Senso. 

Connecting 

The app is connecting to senso and applying any startup policies 

Connected 

The app is connected to senso, the client is online in the web console and modules can be executed. 

Faulted 

The app failed to connect or experienced a critical error that caused it to become disconnected from Senso. 

Reconnecting 

The app has disconnected from Senso and is attempting to restore the previous session. 

 

Quit Button 

If the client enters a faulted state, a Quit button will become available in this menu. If the client is not functioning as expected and the quit button is not available, the application can be closed using Activity Monitor (Applications > Utility > Activity Monitor). 

 

Log Files 

Log files can be found in the Collateral Directory.  

 

The naming convention is “SensoClient_DAY_MONTH_YEAR.log”. All logged events are recorded in this file, the following log levels are available: 

TRACE 

Verbose diagnostics intended to help troubleshoot the state of the application 

DEBUG 

Detailed diagnostics intended to help diagnose the state of the application 

INFORMATION 

Useful information about the state of the application 

WARNING 

Any event where the client encountered an unexpected state that may affect operations 

ERROR 

Any exception thrown during the application 

FATAL 

Any error that causes the system to crash 

 

In the current build, all logging levels are enabled and will be written to the file. In the future a config option will be added to hide logs above a specified level.