-
Type:
Bug
-
Resolution: Answered
-
Priority:
High
-
Component/s: Forge - App UI Web
-
None
-
Major
Issue Summary:
Forge app CSP blocks documented default emoji CDN host
pf-emoji-service--cdn.us-east-1.prod.public.atl-paas.net
As workaround partner would have to add external permissions, potentially forcing a major version and affecting Runs on Atlassian expectations.
Steps to Reproduce
Minimal Forge app: emoji-repro.zip![]()
- Create/load a Forge Custom UI app.
- Render a plain <img> using https://pf-emoji-service--cdn.us-east-1.prod.public.atl-paas.net/...
- Observe browser console/network.
Expected Results
- The documented default allow-listed host should load without requiring manifest egress.
Actual Results
- Browser reports CSP violation for the CDN host.

Workaround
- To render emojis in your app, internal APIs are used to access the list of emojis available. We’ve allow-listed the following:
- api.atlassian.com/gateway/api/emoji/ for fetch.client to list emojis
- Or add external permissions, potentially forcing a major version and affecting Runs on Atlassian expectations.
- relates to
-
ECO-1504 Forge app emoji rendering/fetch behavior is inconsistent with documented emoji guidance and appears to require non-Runs-on-Atlassian external permissions
-
- Closed
-