A forge app adopted from connect is unable to be installed (still uses connectModules from manifest.yml)

Forge
1

Hello,

I am aware of the fact that is it no longer possible to install private connect apps (https://developer.atlassian.com/platform/forge/changelog/#CHANGE-3096).

But recently I have noticed that apps which have been adopted from connect (no longer using atlassian-descriptor.json, but rather manifest.yaml with connectModules key) are not possible to be installed on any jira/confluence instance via forge install. The installation fails every single time (does not matter if the app is private, or it is publicly listen on marketplace and just installing dev version of it on private jira instance).

I tested it with removing connectModules and keeping only connect.key - also did not work. App installation failed. Tested multiple apps - every single installation failed.

This is why I wanted to ask if there has been any change preventing from installing also connect apps that were adopted from forge.

EDIT: just to provide more context - after additional testing this seem to be happening on just single Jira url - not on others.

2

Hey there Ivan!

This is an interesting observation and we want to make sure we can help you properly. Could you raise a support ticket with further information about your issue so that our engineers can help investigate further?

Thanks!

3

Hi Vincent, sure, I’ll proceed with creating a ticket.