Description
Issue Summary
As reported by several people on CONFCLOUD-67710 and on the community forum (https://community.developer.atlassian.com/t/getting-referenceerror-ap-is-not-defined/19780/11) the following error and stacktrace appear in the console:
ReferenceError: "_AP is not defined" > <anonymous> https://d2oo471t4e338f.cloudfront.net/XXXXXXX.atlassian.net/wiki/s/d41d8cd98f00b204e9800998ecf8427e-CDN/-659307766/h/5295cb211c06107e38861d05bc31dea1/_/download/batch/com.atlassian.plugins.atlassian-connect-plugin:iframe-host-utils-v5/com.atlassian.plugins.atlassian-connect-plugin:iframe-host-utils-v5.js?externals=__local-default__:5 > com.atlassian.plugins.atlassian-connect-plugin:iframe-host-utils-v5.js:1:96
Steps to Reproduce
I've found it can be reliably reproduced on Chrome via:
- Create a new page from a connect app blueprint containing a static content macro
Expected Results
no console errors
Actual Results
The below exception is thrown in the console:
ReferenceError: "_AP is not defined" > <anonymous> https://d2oo471t4e338f.cloudfront.net/XXXXXXX.atlassian.net/wiki/s/d41d8cd98f00b204e9800998ecf8427e-CDN/-659307766/h/5295cb211c06107e38861d05bc31dea1/_/download/batch/com.atlassian.plugins.atlassian-connect-plugin:iframe-host-utils-v5/com.atlassian.plugins.atlassian-connect-plugin:iframe-host-utils-v5.js?externals=__local-default__:5 > com.atlassian.plugins.atlassian-connect-plugin:iframe-host-utils-v5.js:1:96
Workaround
Currently there is no known workaround for this behavior. A workaround will be added here when available