Uploaded image for project: 'Atlassian Ecosystem'
  1. Atlassian Ecosystem
  2. ECO-70

License type object returned by view.getContext() in `@forge/bridge` does not have the new structure

    • Minor

      Issue Summary

      From this change log https://developer.atlassian.com/platform/forge/changelog/#CHANGE-1179 , the license details were changed, and as well on the docs that it was changed too. However, the library @forge/bridge still has the old library structure:

       

      export interface FullContext {
          accountId?: string;
          cloudId?: string;
          extension: ExtensionData;
          license?: LicenseState;
          localId: string;
          locale: string;
          moduleKey: string;
          siteUrl: string;
          timezone: string;
      }
      interface LicenseState {
          isActive?: boolean;
      }

       

      Steps to Reproduce

      1. Have a Custom UI Forge app.
      2. Use the view bridge module https://developer.atlassian.com/platform/forge/custom-ui-bridge/view/#example-2.
      3. The old license structure still returns.

      Expected Results

      New structure.

      Actual Results

      Old structure.

      Workaround

      Currently there is no known workaround for this behavior. A workaround will be added here when available

            [ECO-70] License type object returned by view.getContext() in `@forge/bridge` does not have the new structure

            Dave added a comment -

            This should now be resolved, please add a comment if you find that you find that there are still problems with it.

            Dave added a comment - This should now be resolved, please add a comment if you find that you find that there are still problems with it.

            Dave added a comment -

            This should be available now as the changes have been rolled out to all regions.

            Dave added a comment - This should be available now as the changes have been rolled out to all regions.

            Dave added a comment -

            I've linked this issue with https://jira.atlassian.com/browse/ECO-73 as it is related.

            The changes announced only relate to license checking Custom UI and not UI Kit 1 (I'm adding this information that anyone coming across this related issue). We have released a general update for Forge Custom UI, but we are still waiting for an additional update specifically for Forge Custom UI applications running on Jira (this is being rolled out today).

            I'll add another update when the Jira change is complete, and will update the status of this issue.

            Dave added a comment - I've linked this issue with https://jira.atlassian.com/browse/ECO-73 as it is related. The changes announced  only relate to license checking Custom UI and  not  UI Kit 1 (I'm adding this information that anyone coming across this related issue). We have released a general update for Forge Custom UI, but we are still waiting for an additional update specifically for Forge Custom UI applications running on Jira (this is being rolled out today). I'll add another update when the Jira change is complete, and will update the status of this issue.

            Hi,
            Could you please provide me with an update?
            Customers who use our product without a license can't be blocked, so we lose a lot of money!
            This ticket needs to be fixed ASAP!

            Naor Shirazi added a comment - Hi, Could you please provide me with an update? Customers who use our product without a license can't be blocked, so we lose a lot of money! This ticket needs to be fixed ASAP!

              Unassigned Unassigned
              d6427b6fb657 Guilherme Bueno (Inactive)
              Affected customers:
              0 This affects my team
              Watchers:
              5 Start watching this issue

                Created:
                Updated:
                Resolved: