Private Connect App Does Not Appear After Install on New Instances

Hello everyone,

We’re currently migrating our apps from Atlassian Connect to Forge.
The Forge-from-Connect migration step is completed, but with the automated migration program on hold, we now have customers running either our Connect app or our new Forge app.

We’re still actively developing features for both versions, and for each release we spin up new test instances. Since most customers still use the Connect version, we continue installing the app as a private Connect app (aka. the good old ways).

The issue:

  • The private app installs without errors.

  • But after installation, the app does not appear at all in the “Manage apps” screen.

  • Because the app is missing from the list, we cannot enter the private token, meaning we can’t configure or use the instance at all.

Even Atlassian’s own apps/products don’t appear — the whole app list is empty, so the instance is effectively unusable for testing.

Has anyone run into this situation?
Is this a known issue with private Connect apps or with mixed Connect/Forge migrations?

Any hints would be greatly appreciated!

This topic was automatically closed after 30 days. New replies are no longer allowed.