-
Type:
Bug
-
Resolution: Unresolved
-
Priority:
Low
-
Component/s: Forge and Connect - Developer Documentation
-
None
-
Minor
Issue Summary:
The emoji API endpoint (https://api.atlassian.com/gateway/api/emoji/) returns an imagePath field in the response, but this value cannot be reliably used as an image source in Forge or Runs on Atlassian apps. There is no documented or supported way to transform the imagePath into an allow-listed CDN URL on pf-emoji-service--cdn.us-east-1.prod.public.atl-paas.net, and the API does not expose a ready-to-use CDN URL.
Steps to Reproduce
- Call the emoji metadata endpoint: GET https://api.atlassian.com/gateway/api/emoji/standard?scale=XHDPI&preferredRepresentation=IMAGE
- Read the imagePath field from the response for any emoji
- Attempt to use that imagePath value as an <img src> in a Forge app
Expected Results
The emoji API should return a fully qualified, CDN-safe image URL that is compatible with Forge's allowlist/CSP model, or documentation should describe how to construct a valid CDN URL from the returned metadata.
Actual Results
The imagePath returned by the API is not a fully qualified URL and cannot be used directly in Forge apps due to CSP restrictions. There is no documented transformation from imagePath to a valid CDN URL on the allow-listed host (pf-emoji-service--cdn.us-east-1.prod.public.atl-paas.net).
Workaround
No workaround AFAIK.
- is related 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
-
- Long Term Backlog
-