Hi everyone,
I’m trying to publish an update for my Forge app listing, but I’m blocked by a Marketplace versioning error and I’m not sure what the correct process is in this case.
What I did:
- updated the app manifest
- added new scope permissions
- deployed to production using:
- forge deploy -e production
After that, when I try to create a new Marketplace version, I get the following error:
**Invalid value for field ‘versionNumber’: Must be unique within the same cloud compliance boundary
**
In the Create New Version screen, the version number is auto-filled and I cannot edit it manually.
It looks like Marketplace is trying to use a version number that is already taken, so I cannot proceed with publishing the update.
Would really appreciate any advice from anyone who has run into this before.
Thanks!
Hi @MaksymBabenko, we’ve only been live on Forge for a little while now, but we only needed to “Create Version” the first time (to get to forge).
Subsequent deploys of updates to the manifest auto-created the new version in the marketplace. When you did the deploy did it tell you version 3.4.0 was created? Check the Forge Developer console to confirm that the last production version matches the marketplace version.
The issue in my case seems slightly different.
After forge deploy -e production, the new marketplace version appears to become active/public automatically.
Then, if I try to go through the manual Marketplace version flow, I cannot really adjust it properly, and Marketplace throws a duplicate version number error because that version is apparently already taken.
So the problem is that the version seems to be auto-created/activated before I can manage the release normally.
Same problem. Cannot resubmit the app
In our case, the issue was resolved by selecting the appropriate app version in the Atlassian Marketplace ( Log in with Atlassian account ) and completing and saving all newly introduced fields that had been added since the last release. The following configuration was required:
