@forge/bridge requestJira stopped working: An unexpected error occurred when fetching an auth token

In my Forge custom UI app, calls to requestJira will then throw an error as in the picture:

This error happens after I upgraded @forge/cli from 2.0.1 to 2.0.2. Then I downgrade it to 2.0.1 but the problem is still there.

The exact request which causes the problem:

  • requestJira('/rest/api/3/issuetype')
  • requestJira('/rest/api/3/project')

One thing I noticed is that previously, those calls will send directly to a Jira instance endpoint such as https://someJiraHash.net/rest/api/3/project, but now it sends the request to a graphql server https://mySite.atlassian.net/gateway/api/graphql (just like it did before @forge/bridge@2.0.0, see the change log: Forge bridge version 2.0.0)

I tried to upgrade @forge/bridge to the latest version but it did not help.

Can anyone provide some help?

3 Likes

Any answer from Atlassian Staff?

As @nhac.tat.nguyen has already noticed, I have a similar issue on the Confluence side: Error getting users from Confluence with @forge/bridge
Considering I didn’t change anything, what am I doing wrong?

Same here. We already requested that:
https://ecosystem.atlassian.net/browse/FRGE-465

Thanks

1 Like

Hi @nhac.tat.nguyen

We have had an incident last week whereby the Consent Flow would not succeed for some Custom UI apps (see: App authorization requires manual refresh).

In some cases, the requestJira or requestConfluence of the @forge/bridge methods appear broken. In order to fix it, you can revoke the existing app permissions via the Admin page of your Atlassian site.

There, you can go to Connected Apps → Select your app → Manage → Select the user having trouble with the app → Revoke permissions

When this is done, the user will be able to re-trigger the Consent Flow and the auth token retrieval should now be resolved.

Hope this helps.

Sorry for the inconvenience caused.

2 Likes

Thank @Xavier, it works now!

1 Like