The JavaScript runtime exited unexpectedly error from google add-on

[Budhitha Perera]

Hello,

I'm working on the Oneflow workspace add-on in Google Workspace. Suddenly we got the error from Google's side. Google Cloud console log as follows.

{
  "insertId": "-lcueyeb4s",
  "jsonPayload": {
    "deploymentFunction": "getHomePage",
    "error": {
      "code": 3,
      "message": "The JavaScript runtime exited unexpectedly."
    },
    "@type": "type.googleapis.com/google.cloud.gsuiteaddons.logging.v1.GSuiteAddOnsLogEntry",
    "deployment": "********************************"
  },
  "resource": {
    "type": "g_suite_add_ons",
    "labels": {
      "project_id": "oneflow-apollo-add-on",
      "deployment": "**************************************"
    }
  },
  "timestamp": "2024-10-15T14:19:37.327721Z",
  "severity": "ERROR",
  "logName": "projects/oneflow-apollo-add-on/logs/gsuiteaddons.googleapis.com%2Ferrors",
  "receiveTimestamp": "2024-10-15T14:19:37.921606018Z"
}

Could someone explain to me what was the exact issue here?

Thank you.

[Stanislav Tvarůžek]

I'm having the same issue. Add-ons in production have begun to return this error.

The add-ons use the V8 engine.

The sidebar won't even open.

From logs I see:

resource: {

labels: {

function_name: "showSidebar"

invocation_type: "menu"

project_id: "********"

}

type: "app_script_function"

}

severity: "ERROR"

timestamp: "2024-10-16T12:07:30.950Z"

showSidebar function:

SpreadsheetApp.getUi().showSidebar(
HtmlService.createTemplateFromFile('sidebar.html').evaluate()
.setSandboxMode(HtmlService.SandboxMode.IFRAME)
.setTitle('ABCD'));

[Jarrod Clark]

I have been having this same issue for the past couple days. I have narrowed it down to a styling issue. It is either a component in my custom CSS or CORS bootswatch from cdn. I scaled down my styling and was able to get my app to load in a minimally functional form. Could this be what is happening for you Stanislav?

[Budhitha Perera]

It's working again without our intervention. I don't know what happened those days, but I can guarantee it was from Google's side.