Hi guys,
I started having some trouble with a new Forge app I’m trying to develop.
Deployed it in development environment, installed in a brand new developer cloud site, and worked fine.
But last friday, (out of nowhere) it started requiring to grant access permissions:
And when I go to Allow Access, death comes:
Notice it was registered as a new app, installed in a new site, by an org admin user, deployed by the same forge user with a new API token…all new.
Don’t know what else I can do, anybody has some light?
Something weird I noticed is that when I run forge install, it warns me:
The scopes or egress URLs in the manifest are different from the scopes in your most recent deployment to development. Try running forge deploy -e development before installing.
EVEN WHEN I HAVE JUST RAN FORGE DEPLOY!
These are my permissions in manifest:
permissions:
scopes:
- read:jira-work
- read:email-address:jira
- read:app-system-token
- read:app-user-token
- storage:app
- read:app-data:jira
- write:app-data:jira
- manage:jira-project
content:
scripts:
- unsafe-hashes
- unsafe-eval
- unsafe-inline
styles:
- unsafe-inline
external:
fetch:
backend:
- address: localhost:\*
- address: "\*.atlassian.net"
- address: "\*.atlassian.com"
- address: "\*.atlassian-dev.net"
client:
- address: localhost:\*
- address: "\*.atlassian.net"
- address: "\*.atlassian.com"
- address: "\*.atlassian-dev.net"
remotes:
- key: remote-app
baseUrl: ${REMOTE_URL}
operations:
- compute
auth:
appSystemToken:
enabled: true
appUserToken:
enabled: true
(The REMOTE_URL variable was correctly exported and set in development)