Custom Forge App: Invoke Function Fails with Non-Development Accounts

[Art Hsieh]

I have attempted to develop a Jira Forge app, but I noticed that using the invoke function with any account other than the one used for development always returns the following error:

User did not have access to specified resource(s)

This issue occurs even with the Hello World app or any other app that calls invoke. For example, I tried the following configuration directly from forge create:

• jira:projectPage

• jira:issuePanel

In every case, the same error appears. It seems that the invoke function never reaches the backend logic and is simply rejected when called. With my development account, everything works fine. I’m not sure if any configuration needs to be enabled for the invoke function to work with all accounts, but I couldn’t find any documentation mentioning such a configuration. I even tried enabling sharing under the Developer Console, but the issue persists.

Any assistance would be highly appreciated.

[Petru Simion _Simitech Ltd__]

I have the same issue but I noticed the problem manifests only if when I was impersonating a user.

When the user logged in directly the problem did not manifest.

[Tuncay Senturk _Snapbytes_]

Hi @Art Hsieh 

It is hard to guess what the problem is but I'd say non-developer users will not have access to Forge functions until the app is installed in the Jira instance they are using. If you are testing in development or staging, the app must be explicitly installed to that Jira site.

forge deploy --environment production
forge install --environment production

Also, it is wise to ensure that manifest.yml contains all required scopes. Then, check that any function defined is listed under resources and used correctly in the resolver section.

[Art Hsieh]

Thank you for the advice, @Tuncay Senturk _Snapbytes_ 

The apps I tried were successfully deployed and installed with the production environment, but none seem to work. Please note that, to simplify the issue, the Forge apps I'm testing are exactly as generated by `forge create` - with no modifications to the manifest.yml. I can confirm they function correctly when run with my development account, so I don't believe this is a scope issue.

[Petru Simion _Simitech Ltd__]

We have the same problem.

In order to eliminate any issues created by our code we tested a simple Hello World application created by using the forge create command.

Same issue manifests.

If the developer executes it it works fine. The issue panel shows first message Loading, then the backend returns a string and this string is replacing the Loading.

If any other user is impersonated, the Loading message stays forever, and the Developer Tools shows the error -> User does not have access to resource(s).

Since we did not alter any code, how comes a template results in errors?

We deployed the app in prod, so this is not the cause.

Also we deployed via forge install -e production but also shared and used the link.

Same problem.