Test Transition from Connect to Forge in Production

[AndrewTyson]

Hi All,

I have migrated a Connect Confluence Macro from Connect to Forge. Sharing is enabled, and the Forge app is deployed to Production.

Before submitting the successor Forge App to Marketplace I want to ensure that the transition will work in a test environment - specifically that existing space pages with the Connect macro continue to work.

I have an existing Confluence test environment with the licensed Connect Application installed from MarketPlace. The test environment has space pages with the Connect macro.

When I try and install the Forge successor app from the command line using forge install -e production I get the following error.

Request ID: b30283f89e9b4acdaf362dbaf6e8fdcc
Result: {
  "appInstallationTask": {
    "state": "FAILED",
    "errors": [
      {
        "message": "Failed to license app for product confluence because this app has not been configured to support this product",
        "extensions": {
          "errorType": "MISSING_LICENSE_FOR_PRODUCT",
          "statusCode": 400
        }
      }
    ]
  }
}

Error: Failed to license app for product confluence because this app has not been configured to support this product

Error: Failed to license app for product confluence because this app has not been configured to support this product
    at InstallationsGraphqlClient.monitorAppInstallOrUpgrade (/usr/local/lib/node_modules/@forge/cli/out/installations/graphql-client.js:202: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:150: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:185:34)
    at async /usr/local/lib/node_modules/@forge/cli/out/command-line/register-installation-commands.js:35: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)

The test environment has the development version of the Forge App installed fine.

Do I need to unsubscribe from / unistall the MarketPlace Connect App before installing the Forge production instance?

Thanks and regards,
Andrew

[SreejaGupta]

Hey @AndrewTyson no need to unsubscribe/uninstall the marketplace Connect app.
You can only test your Forge successor’s license states in non-production environments (documentation here https://developer.atlassian.com/platform/marketplace/listing-forge-apps/#testing-your-app-with-different-license-states )

When you wish to test the update of a Connect app to its Forge successor through a marketplace update, you can raise an ECOHELP ticket with us so we can organise a staged rollout for you (Listing your Forge successor app on Marketplace )

Let me know if you have any other questions