"forge build" command starting to fail with "invalid json response..." error

Forge
1

This morning, when trying to execute: “forge build” I get errors like below. Any idea what is going on? Yesterday all was ok.

If I try to open the URL mentioned in the error I get a 404 error.

Thanks.

root@LP-AST03526:/opt/RD/JiraCustomFieldPlugin/forge# forge build --verbose
Building and uploading your app.
Press Ctrl+C to cancel.

Running forge lint...

Error: invalid json response body at https://developer.atlassian.com/cloud/jira/service-desk/swagger.v3.json reason: Unexpected end of JSON input

Error: invalid json response body at https://developer.atlassian.com/cloud/jira/service-desk/swagger.v3.json reason: Unexpected end of JSON input
    at lint (/root/.nvm/versions/node/v24.15.0/lib/node_modules/@forge/cli/node_modules/@forge/lint/out/lint/lint.js:131:15)
    at process.processTicksAndRejections (node:internal/process/task_queues:104:5)
    at async LintService.run (/root/.nvm/versions/node/v24.15.0/lib/node_modules/@forge/cli/out/service/lint-service.js:30:29)
    at async BuildController.verifyPreBuild (/root/.nvm/versions/node/v24.15.0/lib/node_modules/@forge/cli/out/command-line/controller/build-controller.js:71:33)
    at async BuildController.run (/root/.nvm/versions/node/v24.15.0/lib/node_modules/@forge/cli/out/command-line/controller/build-controller.js:49:13)
    at async /root/.nvm/versions/node/v24.15.0/lib/node_modules/@forge/cli/out/command-line/register-build-commands.js:48:16
    at async Command.actionProcessor (/root/.nvm/versions/node/v24.15.0/lib/node_modules/@forge/cli/out/command-line/command.js:283:28)
    at async Command.parseAsync (/root/.nvm/versions/node/v24.15.0/lib/node_modules/@forge/cli/node_modules/commander/lib/command.js:1104:5)
    at async Command.parse (/root/.nvm/versions/node/v24.15.0/lib/node_modules/@forge/cli/out/command-line/command.js:165:13)
    at async main (/root/.nvm/versions/node/v24.15.0/lib/node_modules/@forge/cli/out/command-line/index.js:94:5)
root@LP-AST03526:/opt/RD/JiraCustomFieldPlugin/forge#
2

I have the same issue. It was working previously. Interestingly it works for one of my colleagues and doesn’t work for another one.

3

I have the same issue.

4

It’s working properly now.

5

The forge lint command downloads the swagger files for Atlassian REST endpoints so that it can check for missing scope declarations in your manifest. It looks like, for some reason, the CLI is not receiving a valid JSON file when attempting to do this.

As a workaround, you can use the --no-verify flag when running forge build, which would bypass the linting checks.