Forge Macro can not be exported as PDF

Hey everyone,

I have a problem with the PDF page export in Confluence Cloud.
I am trying to include a Macro in the page export. It works fine when I export the page as a Word document or if I look at it in the page comparison (see screenshot below). But when exporting the page as a PDF I only get „Error loading the extension!“. (Not even the console.log gets triggered.)

The real Macro is build with Custom UI Components. But even with a dummy Macro (build with UI Kit Components only) the PDF export does not work.

Here is my manifest.yml:

    - key: export-ui-kit-hello-world
      function: main
      title: export-ui-kit
      description: Inserts Hello world!
        function: exportMacro
    - key: main
    - key: exportMacro
      handler: index.exportMacro

And the index.js

import ForgeUI, { render, Fragment, Macro, Text, useProductContext } from "@forge/ui";

const App = () => {
  console.log("Hello App!")
  return (
      <Text>Hello UI Kit!</Text>

export const run = render(
    app={<App />}
const ExportIt = () => {
  const productContext = useProductContext();
  console.log("product context ", productContext);
   return (<Text>Hello Export!</Text>);

export const exportMacro = render(<ExportIt />);

Am I the only one facing this problem?

Thanks in advance for your help.
Best regard


Hello Julia,

We try to make the export in PDF or Word of our Forge macro works a few weeks ago - by basically doing what you did - and we get the same result: “Error loading the extension!” on both Word and PDF and no log about our function being triggered.

We opened a ticket with Atlassian 3 weeks ago (ECOHELP-2340, its not public) but so far they don’t know what is wrong.


1 Like

Hey @SilvreLestang ,

thanks for your message. At least we are not the only ones with this issue.
Is there any way you could keep me in the loop on your ECOHELP-2340 ticket?

Kind regards


as far as I can see, this issue has now been identified as an Incident and is being addressed:

Best regards,

1 Like

Facing same issue. was this issue resolved?

Hey @OnucheIdoko1,
Unfortunatly it’s not resolved yet.

But Atlassian is offering a workaround.
See this ticket:

Best regards

1 Like

Thanks for the information