Using `os` results in an error `INVALID_CAPABILITY`

Forge
,
1

error PROXY_ERR: Forge platform failed to process runtime HTTP request - 400 - INVALID_CAPABILITY
at handleProxyResponseErrors (webpack://jira-issue-panel-custom-ui/node_modules/@forge/api/out/api/fetch.js:70:1)
at (webpack://jira-issue-panel-custom-ui/node_modules/@forge/api/out/api/fetch.js:26:1)
at process.processTicksAndRejections (node:internal/process/task_queues:103:5)
at async ObjectStoreClient.sendRequest (webpack://jira-issue-panel-custom-ui/node_modules/@forge/os/out/os.js:16:1)
at async ObjectStoreClient.requestJson (webpack://jira-issue-panel-custom-ui/node_modules/@forge/os/out/os.js:23:1)
at async (webpack://jira-issue-panel-custom-ui/src/index.js:50:1)
at async Promise.all (index 0)
at async (webpack://jira-issue-panel-custom-ui/src/index.js:24:1)
at async Object.handler (webpack://jira-issue-panel-custom-ui/node_modules/@forge/resolver/out/index.js:31:1)
at async /private/var/folders/63/n4t1v5px3qd7l7pw81psfll40000gn/T/forge-dist-40263-GieY44y2p49L/forge_wrapper.cjs:2:905507 {
status: 400,
errorCode: ‘INVALID_CAPABILITY’
}

2

Welcome to the Atlassian developer community @lynn,

I can see from that stack trace that you are having a problem with the Forge CLI. Can you tell us more? What command were you running? What are some of the diagnostics like forge whoami and forge version? What operating system are you on?

3

Thank you very much for your reply. I have already solved the issue. It was because I had only registered the EAP for the front end and was missing the EAP for the server side.