Egress permission for page attachments still required despite Forge update

Forge
1

Hi there,

we ran into an egress issue regarding page attachments in our Forge app.

Despite the latest Forge update: Improvements to loading of images and media in Custom UI apps

It is still necessary to add the following external permission in your manifest to display attachment images in a Forge app:

permissions:
  external:
    images: 
      - *.media.atlassian.com

Otherwise, the attachment image will be blocked by the browser.

(Unfortunately, this is the only thing that prevents us from qualifying our app for the Runs on Atlassian badge in the current Codegeist.)

4 Likes
3

Hi @SvenHe - are you running the app in the tunnel? There is a CLI patch going out that will make this work while tunneling, but in the meantime, it should work if you deploy. Let us know if this helps

Edit - actually this could be due to the attachment images. We’re looking into it, but in the meantime, the project does meet eligibility requirements for the Codegeist Runs on Atlassian category. It won’t be disqualified if you submit as is

3 Likes
4

Thanks @kwhite,

Yes, it only affects attachments. Deploying does not solve this issue.

Thanks for your help so far.

Best Regards,
Sven

5

Hey @SvenHe, we have pushed a fix a week ago, has this been resolved now? Thanks!

2 Likes
6

Hi @AngelinaIgnatova,

I can confirm that attachment images are not blocked by the browser anymore. They are displayed fine. Thanks! :white_check_mark:

This works when the app is deployed. But running it via tunnel will still block the images from displaying. :x:

Best regards,
Sven

1 Like