Can't use my own Forge Apps on Jira Cloud

Forge
,
1

As I have already documented here, I was (and still am) having trouble using Forge apps on my Jira Cloud instance that were created, deployed, and installed by a service account.
It was to my surprise that I couldn’t also use forge apps that I created, deployed, and installed with my own user as well:

image
image702×135 3.7 KB

I obviously clicked on the “Allow access” button, but it just took me to a warning screen:

image
image803×646 30.5 KB

I’ve tried changing the apps Distribution settings from “Not Sharing” to “Sharing”:

image
image1200×215 14.3 KB

But that also didn’t work.

Now I’m stuck. Idon’t know what else to do. It really should be that hard to use the apps I developed.

2

Hi @LucasXavierFerreira , are you able to provide us with your appId?

3

Ok, I’ll provide the ID of one app, but honestly, that problem is happening with severall other apps as well (basically all apps I tried creating with either my company’s service account or my own user account).

Here it is: 64ed63a7-66af-4ace-9db9-e049ff63c30c

4

A piece of the log from a attempt at hitting the “Allow access” button:

ERROR 2024-07-17 13:02:02.483 2.0.0 ari:cloud:jira::site/96af8095-297e-40d9-8862-cdfb776718ec 209f562e-6f03-410e-83ff-3c62043e08ec resolver core:function [NEEDS_AUTHENTICATION_ERR: Authentication Required] {
  status: 401,
  serviceKey: 'atlassian-token-service-key',
  options: undefined
} []
5

Now I sort of fixed the issue above, but am facing a new one: the loop between “Allow access” and the screen below:

allow_access_loop
allow_access_loop736×811 30.9 KB

allow_access_loop_02
allow_access_loop_02684×600 19.9 KB

6

Hi @LucasXavierFerreira, thanks for providing us with your appId, I was able to look into the logs and I found a scope read:field.options:jira which doesn’t seem like it is being registered correctly, I will need to bring this up with the Jira team.
In the meantime I wanted to ask you:

  • if you needed to use the granular scope in particular or if you could opt to use the classic scope equivalent (classic scopes are recommended over granular scopes currently).
  • if you required the read:me scope, if not, removing it will allow auto consent, so you don’t need to go down the consent screen.

Apologies about the inconvenience.

7

Hi @BoZhang, thanks for the reply. I’m not sure I understand, though. Should I remove the read:field.options:jira and the read:me scopes from the app manifest.yml file?

8

Hi @LucasXavierFerreira, I am asking if you need to use those particular scopes; if they are not required, then removing them from your app should get you out of being stuck in the consent loop and seeing the consent screen altogether.
But this depends on what your app requires; if you are calling an API that requires these scopes, they will need to remain in your app’s manifest for it to work.
To add a bit more detail:

  • The read:me scope stops automatic consent and you will be shown a consent screen. Your app should still function; you will just have to go through the consent screen.
  • The read:field.options:jira is broken on our end, I’ve notified the Jira team about this one. In the meantime, if you are able to use the classic scope equivalent that should work (the documentation should tell you what the classic scope equivalent for a particular API is, for example)
9

Hi @BoZhang that worked! Thank you.

But it only worked for apps deployed with my own user account.
I still can’t use the apps created, deployed, and installed using the service account.

Do you have any insights on what may be causing this?

10

Hi @LucasXavierFerreira, I’m glad to hear that it’s now working with your own apps. What error are you seeing with the apps created by your service account?

11

@BoZhang It just keeps hanging on “Loading…” forever:

image
image1173×367 6.47 KB

I’m still waiting on the Configuration Management team to extract the logs on this attempt.
As soon as I get a hand of them I’ll share them here.