I’m experiencing a problem on the path to release a Forge app on the Atlassian Marketplace, even before requesting to make it public.
Scenario:
I have an old vendor ID (1217xxx)
I created a new Forge app, with team member using my historical mail address which generated a UUID-like vendor ID (bd647e60-...)
Logging-in Developer console with my historical mail address,
Clicking “Manage vendor account” leads to new UUID-like Marketplace id → a page not found/”Looks like you took a wrong turn”
Cleaning browser cache and logging-in Marketplace with my historical mail, I land on “old” vendor page, listing old apps which should be deleted
Same scenario with a fresh user/Forge app admin team member leads to same vendor UUID-like not found page
Did any of you experienced this kind of problem? I obviously took a wrong turn but I can’t find which one. It looks to me like Forge app vendor account is stuck in an incomplete provisioning state, but this is my intuition.
Being blocked on way to public release I raised an ecosystem ticket ECOHELP-99171 in the meanwhile.
Thanks for your input. Actually your case seems different: in my case, it’s an impossibility to access vendor page associated to a Forge app before even requesting for approval. In other terms, it’s not possible to edit vendor’s page details, and go on with Forge Marketplace process.
It leads to a working Atlassian Market place app details edit page with an app id in the URL which is different from Forge app id shown in Overview section, but it works.
From there, clicking on vendor link works too, showing vendor page with legacy vendor ID: