When we started out with publish our app “build with Forge” back in June 2022, we carefully followed the nice documentation written by Atlassian on how to enable licensing, including the manifest and code to check the presence of an active license.
Now we’ve just been brought to attention that Atlassian announced in the Forge change log a breaking change on how to check the license.
@Atlassian - have I missed something or did you “announce” this just via the Forge changelog???
Ok, so here’s the “paper trail”:
- The “how to” as it was just a few months back (thanks Internet Archive): https://web.archive.org/web/20230605180347/https://developer.atlassian.com/platform/marketplace/listing-forge-apps/
- The “how to” as it reads today: https://developer.atlassian.com/platform/marketplace/listing-forge-apps/#checking-the-licence-status
- The change log entry about the old way being broken and fixed by introducing a breaking change: https://developer.atlassian.com/changelog/#CHANGE-1184
Quoting #3 here:
license property in context object now has correct active status property
license object returned by
view.getContext() in Custom UI previously had an
isActive property. This property was always
undefined regardless of whether the app had a valid license or not.
This is now fixed with the introduction of a new
license.active will be
true for valid installations and
false otherwise. More details on how to check for the license status can be found here.
EDIT: Had to change the bold FIXED to a quoted “FIXED”. In reality the ‘FIX’ breaks things…