Environment: Figma Make / Vite + React / preview iframe
Error appearing in the Figma Make error panel on every save:
IframeMessageAbortError: Message aborted: message port was destroyed
at a.cleanup (figma_app-a1e03f1c19341be6.min.js.br:536)
at o.cleanup (1039-3b55194fb03a991d.min.js.br:1070)
at eS.setupMessageChannel (figma_app-a1e03f1c19341be6.min.js.br:536)
at e.onload (figma_app-a1e03f1c19341be6.min.js.br:536)
Problem: This error appears in the Figma Make error panel every time the preview iframe refreshes (e.g. after saving a file). The entire call stack consists exclusively of Figma's own minified code (figma_app-*.min.js.br, 1039-*.min.js.br) — there is not a single frame from the application code.
Root cause: Figma's setupMessageChannel fires on the new iframe onload and attempts to clean up the old MessagePort from the previous load. That port was already destroyed by the browser when the iframe navigated → IframeMessageAbortError is thrown inside Figma's own parent-frame JavaScript.
What I have tried (none of it works):
window.onerror handler returning true to suppress
window.addEventListener('error', ..., { capture: true }) with preventDefault() + stopImmediatePropagation()
window.addEventListener('unhandledrejection', ..., { capture: true }) suppression
MessagePort.prototype wrapping (postMessage / close / start)
Full console.error / console.warn / console.log override
EventTarget.prototype.dispatchEvent override for error and unhandledrejection events
Outgoing window.postMessage filter (to block any error relay to the parent)
window.reportError override (Chrome 95+)
Error constructor override (to neutralise the error object at construction time)
Promise.reject override (to auto-attach .catch() on suppressed rejections)
Attempting to patch window.parent — throws SecurityError because the parent frame (www.figma.com) is cross-origin relative to the preview iframe (*.makeproxy-m.figma.site)
Conclusion: The error is thrown inside www.figma.com's JavaScript context (the parent frame). The preview iframe is cross-origin — it is completely impossible to intercept, patch, or suppress anything in the parent frame from within the iframe. The Figma Make error panel appears to collect this error directly from the parent frame's own error tracking system, bypassing every standard web API available to the iframe.
Questions:
Is this a known issue?
Is there any supported way to suppress this error, or is it purely cosmetic noise from Figma Make's own infrastructure?
Is the Figma Make team planning to fix this so it doesn't appear in the error panel and confuse developers into thinking the bug is in their own code?
This fires on every single save in Figma Make and is very misleading — it looks like an app crash but has zero effect on functionality.