Forge successor app to private connect app

Forge Adopting Forge from Connect
, ,
1

Hi everyone,

we are currently migrating from connect to forge, using connect on forge as an intermediate step. We do have a private connect app which we use for internal testing before rolling out changes to public, and we would like to test the migration process there first.

However, I cannot upload a forge successor app to the connect app - I just get “Version creation failed

Failed to create app version. Please try again.” when I choose our forge app for the new version.

  • Is this scenario supported at all? I know that it says somewhere “private listings of forge apps are not supported” but I’m unsure what this actually means oO
  • If yes, what am I doing wrong? The app is published to production and sharing is enabled. Any chance to get more information here?

Thanks in advance!
Jasmine

2

Hi @JasmineMller,

I believe that “private listings of forge apps are not supported” might be it, i.e. uploading the new Forge-based version failed because the listing is private, but I’m not the expert.

In any case, you can test the migration process without involving marketplace - simply install the Forge successor over the top of the connect installation using the CLI. The instructions are here and they note:

The process triggered by installing the Forge version over the Connect version is the same one that will later be triggered by admins upgrading to the Forge version of your app

Hope that helps,

Jimi

2 Likes
3

Okay,

unfortunately it doesn’t work with our public app as well.

I have:

  • Enabled licensing in the manifest
  • Pushed the app to production
  • Enabled sharing in the developer console
  • The app is public

From my understanding that is all that is needed. However I still receive the same error when trying to create a new version as a forge app instead of the connector based one.

It is rather infuriating that we get zero information about the actual error. I can only assume that something is amiss, however I have absolutely no clue what the problem might be.

I have raised an ECOHELP ticket, however maybe someone does have an idea.