Forge install against the staging environment fails even though it's deployed to staging

Hi there

I’m trying to reinstall a workflow validator onto a sandbox environment but under a different deployment environment.

We recently fired up a second sandbox and we want to reserve the development deployment environment for the new sandbox, while keeping staging for our current sandbox.

I uninstalled the app from our sandbox (it as installed against the development environment), redeployed to staging forge deploy -e staging and after that completed, i attempted forge install -e staging (and then selecting the product and entering our target site) and it fails with

Error: Forge apps must be deployed before installation. Deploy your app by running forge deploy -e staging.

The dev console shows that my app is deployed to the staging environment. I even tried the full install command forge install -e staging -p Jira -s [oursandboxurl]

and it still fails

the runtime for the workflow validator is nodejs22.x and im running node v22.13.0

Any ideas?

running the install with --verbose, generates the following stacktrace

Error: Forge apps must be deployed before installation. Deploy your app by running forge deploy -e staging.
Error: Forge apps must be deployed before installation. Deploy your app by running forge deploy -e staging.
at InstallController.run ([mydirectory]\AppData\Roaming\npm\node_modules@forge\cli\out\command-line\controller\install-controller.js:204:27)
at process.processTicksAndRejections (node:internal/process/task_queues:105:5)
at async [mydirectory]\AppData\Roaming\npm\node_modules@forge\cli\out\command-line\register-installation-commands.js:22:9
at async Command.actionProcessor ([mydirectory]\AppData\Roaming\npm\node_modules@forge\cli\out\command-line\command.js:270:28)
at async Command.parseAsync ([mydirectory]\AppData\Roaming\npm\node_modules@forge\cli\node_modules\commander\lib\command.js:936:5)
at async Command.parse ([mydirectory]\AppData\Roaming\npm\node_modules@forge\cli\out\command-line\command.js:167:13)
at async main ([mydirectory]\AppData\Roaming\npm\node_modules@forge\cli\out\command-line\index.js:59:5)

Hi @DeonPetrusMeyer

Just as a sanity check what does forge environments list return for your app?

Please provide your app id so we can see if something is amiss here.

Cheers
Joshua

Hi @JoshuaHwang

Here’s my appid: be791c61-bfb4-46f0-8688-dbec02b147bc

All three environments are returned, with staging showing latest deployed to (last week Friday). I have redeployed using cli 11.5.0, no difference.

@forge/cli 11.5.0 has been installed globally but when i run npm -v @forge/cli (with or without -g) it still points to 11.4.1

Not sure if this is a symptom or cause of the issue. I checked the sources for the @forge/cli and it only points to the global location

running forge --version does return 11.5.0 though.

HI @JoshuaHwang

I’ve done other app installs (not workflow validators) in the meantime (to development though) and didnt encounter any issues.

My colleague however reported that other workflow validators he tried to install, are giving the same issue.

I’ve logged an Ecosystem ticket for investigation. Will update this topic once the solution has been found. The devs are investigating.

1 Like

So the issue was found. It was found that the manifest somehow was updated to include a new application id. Due to the mismatching application ids (whats in the manifest vs what has been deployed/ installed) it couldn’t find the deployment.

The errors though were not very intuitive and i happened to check the manifest file along with the dev console when I realised the issue.

As to how it changed, my colleague has no idea but after the application id was corrected in the manifest file, everything worked.