Socket Closed with Enigma

MirelaPopovici — Fri, 21 Feb 2025 21:22:00 GMT

We have a bit of code in javascript using the enigma engine to obtain the first sheet id of an app. It works well in many of the installations.

However, on one environment it fails with a socket closed exception. with a hardcoded sheet id the graphics load and all of the rest apis work as well.

The problem occurs when trying to instantiate the enigma engine in this bit of code:

async function createEnigmaAppSession(schema, appId, identity, params) {
const session = enigma.create({
schema,
url: `wss://${TENANT}/app/${appId}/identity/${identity}?${params}`
});

handleDisconnect(session);

const enigmaGlobal = await session.open();
const enigmaApp = await enigmaGlobal.openDoc(appId);
return [session, enigmaApp];
}

I have triple checked the Content Security Policy with the server name and frameAncestors checked. the web integration id and api key and the private key seems to be ok.

topic Socket Closed with Enigma in Integration, Extension & APIs

Socket Closed with Enigma