Forge app Error: Error performing sync with Connect: Something went wrong while trying to sync your app with Connect

I am having issues with running forge install today on September 14th.

Setup:

  • Nodejs version: nodejs18.x
  • Atlassian product: Jira
  • Atlassian environment: DEV

The last line of verbose output is:

Variables: {
  "id": "<ID>"
}
  ◀️  GraphQL
Request ID: <REQUEST_ID>
Result: {
  "appInstallationTask": {
    "state": "FAILED",
    "errors": [
      {
        "message": "Error performing sync with Connect: Something went wrong while trying to sync your app with Connect. Please contact Atlassian support.",
        "extensions": {
          "errorType": "CONNECT_PLUGIN_CONNECT_SYNC_ERROR",
          "statusCode": 502
        }
      }
    ]
  }
}

Note: I was also doing testing on September 12th (both forge deploy on already installed app to updated it & forge install when I removed my app, to re-install it) and it worked fine then (there was a different issue I noticed that day, related to AWS S3 failing, but that went away through-out the day)

2 Likes

I got the same error when I run forge install -s xzy.atlassian.net -p jira --non-interactive -e staging

Same issue. To highlight that it looks like an overall problem for all Forge apps.

Same issue.
I go through the forge tutorials. If it just simple app without any manifest permission change it installs, but as soon as I add any permission with forge lint --fix or just manually adding it in manifest in permissions->scope: (e.g. read:jira-work / write:jira-work )it fails with:

Error: Error performing sync with Connect: Something went wrong while trying to sync your app with Connect. Please contact Atlassian support.

Same issue observed today when installing App on custom environment

Error: Error performing sync with Connect: Something went wrong while trying to sync your app with Connect. Please contact Atlassian support.

Hi everyone,

Thanks for raising this - we’re looking into it. It looks like this may be recovering now, could you please try installing your app again and let us know if things are working?

Cheers,
Sean

2 Likes

It works for Jira apps, but if any Confluence permissions are required and need to be installed on Confluence - the same issue appeared

Hi @kapitonik,

Thanks for the confirmation. It may take a few more minutes for everything to recover - you should hopefully be able to install via Confluence again shortly.

3 Likes

Fixed confirmed as well for Confluence. Thanks!

Fixed confirmed, works for me. Thanks!

Can confirm the issue is resolved for me - I am able to install my forge app again. Thanks! :muscle:

Working for me now … Thanks

I still have issue when forge install to prodction:

Error: An unexpected error occurred

Error: An unexpected error occurred
    at InstallationsGraphqlClient.monitorAppInstallOrUpgrade (/usr/local/lib/node_modules/@forge/cli/out/installations/graphql-client.js:204:23)
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
    at async InstallationsGraphqlClient.installAppIntoSite (/usr/local/lib/node_modules/@forge/cli/out/installations/graphql-client.js:151:9)
    at async InstallAppSiteCommand.execute (/usr/local/lib/node_modules/@forge/cli/out/installations/install-app-site.js:13:16)
    at async /usr/local/lib/node_modules/@forge/cli/out/command-line/controller/install-controller.js:52:17
    at async CommandLineUI.displayProgress (/usr/local/lib/node_modules/@forge/cli/node_modules/@forge/cli-shared/out/ui/command-line-ui.js:59:28)
    at async InstallController.run (/usr/local/lib/node_modules/@forge/cli/out/command-line/controller/install-controller.js:174:34)
    at async /usr/local/lib/node_modules/@forge/cli/out/command-line/register-installation-commands.js:33:9
    at async Command.actionProcessor (/usr/local/lib/node_modules/@forge/cli/out/command-line/command.js:252:28)
    at async Command.parseAsync (/usr/local/lib/node_modules/@forge/cli/node_modules/commander/lib/command.js:936:5)

my App ID: 5356e638-b5b1-402a-b71e-8602f8b99356

Could you try again with --verbose and share the error output, please?

2 Likes