I have problem in generate installation link for production and I can only deploy my Forge App to production and send it for Atlassian for release purposes but not generate installation link.
These commands in shell not working:
forge install --environment development --license inactive --upgrade
forge install --environment development --license active --upgrade
forge install --environment development --license trial --upgrade
Can this information cause issue in Atlassian Forge App system. I gave access to source code for freelancer to help me in developement and he took his own development instance and shared my App for production and made installation link? Now my App is in two diffent developer consoles.
Hi @matti.kiviharju – Does that mean your app has two different app IDs (one per console), or the same app ID is displayed in both consoles? If it is a single App ID, then you’ll want to ensure it is assigned to a Developer Space that you own.
Tehere is two diffrent App IDs. I think this cause some issue in installation link generation for me but not for this freelancer. And I can only release new App as Forge and not can release my Forge App to current Timesheet for Jira.
If I understand correctly:
- You shared your source code with a freelancer so they could make a new version of your app.
- The freelancer created a new App ID while working in their environment.
- Now you have two App IDs, and you cannot create an installation link. (I assume for the new ID?)
Can you please clarify the problem you need to solve?
- What are you trying to do? Is the existing App version a Connect app or a Forge app? Is it public (Marketplace) or private?
- Which App ID (new or old) are you trying to generate an installation link for? Who owns the App ID (you or the freelancer)?
- What errors are you receiving?
I am not sure who owns what.
I am also made some new App Ids by failure to release my App and App coming to public to Marketplace soon next week.