-
Bug
-
Resolution: Fixed
-
High
-
12
-
Severity 3 - Minor
-
3
-
Issue Summary
For some pages, there seems to be some race condition on load of js or connect js not binded at all which leads to bizarre error messages in console:
The original issue:
Error 1
com.atlassian.plugins.atlassian-connect-plugin:iframe-host-utils-v5.js?externals=_local-default_:1 ReferenceError: _AP is not defined
Error 2
com.atlassian.plugins.atlassian-connect-plugin:module-loader-v5.js?externals=_local-default_:1 TypeError: Cannot read property 'awaitGlobal' of undefined
Error 3
batch.js?externals=_local-default_&locale=en-GB:14 Uncaught Error: undefined missing ac/create
Error 4
com.atlassian.confluence.plugins.confluence-jira-metadata:confluence-jira-metadata-resources.js?externals=_local-default_&locale=en-GB:254 Uncaught TypeError: Cannot read property 'forPlugin' of undefined
was fixed by an improvement on batching js, see internal comment for stash PR. Some vendor's customers were fixed by this, see https://ecosystem.atlassian.net/browse/DEVHELP-3305 but https://ecosystem.atlassian.net/browse/DEVHELP-3297 had a different issue. Balsamiq's customers were good on newly created pages but are encountering a totally different issue on other pages.
Steps to Reproduce
- Access sample page added as internal comment and see tons of errors
- Access sample page added as internal comment and the previews are okay
Expected Results
There should be no issue displaying these apps
Actual Results
Tons of errors in console and a 404 in synchrony
The below exception is thrown in the xxxxxxx.log file:
j
query-min.js:1 POST https://synchrony.atlassian.com/v1/data/-19ceeb29-cf6c-3958-91ed-67ea6264a60c/confluence-783482968?state-at=@head&state-format=type-tagged&rewrite-request=true&cached=true 404
com.atlassian.plugins.atlassian-connect-plugin:ap-navigator-v5.js?externals=__local-default__:33 no context function defined
getLocation @ com.atlassian.plugins.atlassian-connect-plugin:ap-navigator-v5.js?externals=__local-default__:33
b._handleRequest @ com.atlassian.plugins.atlassian-connect-plugin:ap-core-v5.js?externals=__local-default__:52
c._receiveMessage @ com.atlassian.plugins.atlassian-connect-plugin:ap-core-v5.js?externals=__local-default__:65
com.atlassian.plugins.atlassian-connect-plugin:ap-core-v5.js?externals=__local-default__:38 ACJS: cannot track loading end analytics
{see-all-unresolved-comments__has-unresolved-comments__20575219: {…},
com.balsamiq.mockups.confluence__mockup__37fadeb6: {…},
com.balsamiq.mockups.confluence__mockup__120038d6: {…},
com.balsamiq.mockups.confluence__mockup__37bd1791: {…}, com.balsamiq.mockups.confluence__mockup__7180f73:
{…}, …
}
com.balsamiq.mockups.confluence__mockup__1be6bd21: {
addon_key: "com.balsamiq.mockups.confluence",
key: "mockup",
url: "https://bas20.balsamiq.com/bw-atlassian/confluence…MyNH0.2K9v9Lq4O28ZDZTgw6eHkSd0icpA8s0SRhb78LbbuEY",
options: {…},
id: "com.balsamiq.mockups.confluence__mockup__1be6bd21",
…}
com.balsamiq.mockups.confluence__mockup__2ebc88bf: {
addon_key: "com.balsamiq.mockups.confluence",
key: "mockup",
url: "https://bas20.balsamiq.com/bw-atlassian/confluence…MyNH0.szA1ky_5H0Jtu_-QLz6mJRwDbdvRSVU3xKb9erfzqCI",
options: {…},
id: "com.balsamiq.mockups.confluence__mockup__2ebc88bf",
…}
rzisoftware.atlassian.net-1566881934976.log
Notes
- A PR was made to improve batching and fix other vendor's problems but this is consistent with sample page added as internal comment
- Clearing cache doesn't help
- The wireframes are shown when Confluence is first opened. But a refresh makes them disappear and leave a gap. Vendor's customers have to close Confluence to make them reappear
- From vendor: Jira macro prevents Balsamiq Wireframes content appearing in Confluence page.
Impact of issue
- Balsamiq has total of 2,701 total customer install
Workaround
Currently there is no known workaround for this behavior. A workaround will be added here when available
- depended on by
-
JST-510519 Loading...
-
- relates to
-
-
-