To check that the Signiant App is located in the installation directory: If the application is correctly installed, its components will appear in the installation directory. Newer versions can communicate via WebSockets.Ĭheck for Signiant App in installation directory Received Session Read from App (via websocket/pubnub) - If the Signiant App version was released before March 2018, it will only connect via PubNub.Note: On Firefox, these WebSocket errors may appear outside the collapsed Set up App communication section. The other three ports log a failed WebSocket connection error. The Signiant App tries to connect using four ports and only keeps the first port that responds. Set up App communication - This message is a section heading that can be expanded to show details of the connection attempts and errors.Open your browser console and look for messages that typically appear:.
If some of these messages are missing, it could indicate that the browser has not successfully made a connection to the Signiant App.
When the Signiant App is correctly installed, certain messages are logged in the browser’s console panel when a user opens portal pages. You can identify possible problems with the installation of the Signiant App using three methods: Check for messages that indicate installation Troubleshooting Signiant App Installation To enable application logging, set the log level in the SigniantClient.json file.
#Signiant media shuttle plugin upgrade
For macOS troubleshooting information, see the Signiant App Troubleshooting Guide - macOS.īefore troubleshooting issues with older versions of the Signiant App, it is recommended that you upgrade to the latest version of the application.