How to test Build Editions on Forge?

[AbhishekRay]

Hey,

We are in the process of migrating our Connect app to Forge. We are also working on introducing Build Editions to our app.

I haven’t been able to figure out how to test the Build Editions.

These are the steps I followed:

1. How to adopt Forge from Connect

• Ran these commands and created a development version of the app to test changes out
• I do see “Dev” next to my earlier Connect app which I guess means that the forge adoption worked?

2. https://developer.atlassian.com/platform/marketplace/app-editions-forge-apps/#3--test-the-editions-of-your-app
   1. Added editionsEnabled: true
   2. Ran forge deploy and forge install --environment development --license Advanced

However, I am still not seeing the license being set to Advanced. Neither am I seeing the “Edition” being set in the apps admin page.

What am I missing here?

Thanks!

[SeanBourke]

@AbhishekRay,

Utilising forge install --environment development --license advanced should modify the license context you see in your Forge app, or modify the capabilitySet QSP sent in your Connect iFrame.

Please note that this does not support upgrades today - you would need to uninstall and reinstall the app to override the license state.

[AbhishekRay]

Okay re-installing helped fix the capability context in the app. I am migrating over from Connect. In connect, we would get a lifecycle event with the new permission - I am not seeing that happen during forge testing? How do I make that happen?