-
Bug
-
Resolution: Fixed
-
High
-
12
-
Severity 3 - Minor
-
3
-
논문 요약
일부 페이지에서는 js를 로드하거나 연결 js가 완전히 압축되지 않고 경쟁이 있는 것으로 인해, 그렇기 때문에 설명에 응답하셨을 것으로 표시됩니다.
원래 문제:
오류 1
com.atlassian.plugins.atlassian-connect-plugin:iframe-host-utils-v5.js?externals=_local-default_:1 ReferenceError: _AP가 정의되지 않았습니다.
오류 2
com.atlassian.plugins.atlassian-connect-plugin:module-loader-v5.js?externals=_local-default_:1 TypeError: 정의되지 않은
'awaitGlobal' 속성을 동일하게 사용할 수 없습니다.
오류 3
Batch.js?externals=_local-default_&locale=en-GB:14 포함되지 않은 오류: 정의되지 않은 ac/create가 없습니다.
오류 4
com.atlassian.confluence.plugins.confluence-jira-metadata:confluence-jira-metadata-resources.js?externals=_local-default_&locale=en-GB:254 Uncaught TypeError: 정의되지 않은
'forPlugin' 속성을 사용할 수 없습니다.
js를 개선하여 장식했습니다. stash PR에 대한 내부 설명을 참조하세요. 일부 공급 업체의 고객은 이것으로 기념했습니다. https://ecosystem.atlassian.net/browse/DEVHELP-3305를 참조하세요. 하지만 https://ecosystem.atlassian.net/browse/DEVHELP-3297은 다른 문제가 발견되었습니다. Balsamiq의 고객이 새로 만든 페이지에서는 훌륭하지만 다른 페이지에서는 완전히 다른 문제가 발생했습니다.
재현 단계
- 내부 댓글로 추가된 샘플 페이지에 액세스하여 수많은 오류를 확인하세요.
- 내부적으로 추가된 내용 페이지에 액세스하고 미리 보기가 괜찮습니다.
기대되는 결과
이러한 앱을 표시하는 데는 문제가 없어야 합니다.
실제 결과
콘솔에 수많은 오류가 있다고 404가 있습니다.
아래 이벤트는 xxxxxxx.log 파일이 발생했습니다.
제이
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 -요청=true&캐시=true 404
com.atlassian.plugins.atlassian-connect-plugin:ap-navigator-v5.js?externals=__local-default__:33 매크로 함수가 정의되지 않음
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._수신메시지 @ 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: 로드 중단 분석을 추적할 수 없음
{모든 미해결 댓글 보기__미해결 댓글 있음__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",
키: "모형",
url: "https://bas20.balsamiq.com/bw-atlassian/confluence…MyNH0.2K9v9Lq4O28ZDZTgw6eHkSd0icpA8s0SRhb78LbbuEY",
옵션: {…},
아이디: "com.balsamiq.mockups.confluence__mockup__1be6bd21",
…}
com.balsamiq.mockups.confluence__mockup__2ebc88bf: {
addon_key: "com.balsamiq.mockups.confluence",
키: "모형",
url: "https://bas20.balsamiq.com/bw-atlassian/confluence…MyNH0.szA1ky_5H0Jtu_-QLz6mJRwDbdvRSVU3xKb9erfzqCI",
옵션: {…},
아이디: "com.balsamiq.mockups.confluence__mockup__2ebc88bf",
…}
rzisoftware.atlassian.net-1566881934976.log
고대
- 배치를 개선하고 다른 공급업체의 문제를 해결하기 위해 PR이 작성되었지만 내부적으로 추가된 샘플 페이지와 일치합니다.
- 캐시를 종료해도 도움이 되지 않습니다.
- Wire 프레임은 Confluence를 처음 열었을 때 표시됩니다. 그러나 새로 고침을 받으면 취소되고 꺼지게 됩니다. 공급업체의 고객은 Confluence를 닫아야 다시 확인합니다.
- 공급업체: Jira로 인해 Balsamiq Wireframes 컨텐츠가 Confluence 페이지에 표시되지 않습니다.
인공위성
- Balsamiq의 총 고객 설치 수는 2,701개입니다.
해결 방법
현재 동작에 대한 촬영 방법은 없습니다. 처리 방법이 추가로 필요합니다.
- depended on by
-
JST-510519 You do not have permission to view this issue
-
- relates to
-
HOT-88895 Loading...
-
-
[CONFCLOUD-67710] Problem loading macros in the new editor. Getting 404 in synchrony and js events not binded
Well, this issue is still a problem in the old editor.. but in the new editor the bug does not present itself.
@Sami this is still happening for us in some instances (also customers). The error message is the one from the original issue "ReferenceError: _AP is not defined" and "JWT is expired and no content resolver was specified" when trying to insert a macro.
This happens for some of our test instances (yasoon-tobi.atlassian.net), and at least one of our customers is affected. It seems to be a race condition, since it does not happen all the time, some observations:
- It only happens after creating a new page (before saving) in the new editor
- After a page reload (even only on the draft) it does not happen anymore
- After saving the page it does not happen
- If does seem to happen more often if you disable cache with dev tools open (probably race condition / timing issue). Though our customer certainly does not have dev tools open, so this can occur under "normal" circumstances
Thanks
amotsjonov That's not the same error. The error message there is `_AP is not defined`. Please raise a separate ticket for this one 
Hi, I am just started using confluence to develop add-ons and when I create new page I am getting same error (note that i have 'disable cache' in network tab) so it still seems to be some race condition causing the issue.
Console output:
com.atlassian.plugins.atlassian-connect-plugin:iframe-host-utils-v5.js?externals=_local-default_:formatted:5 ReferenceError: _AP is not defined
at com.atlassian.plugins.atlassian-connect-plugin:iframe-host-utils-v5.js?externals=_local-default_:formatted:11
WRMCB @ com.atlassian.plugins.atlassian-connect-plugin:iframe-host-utils-v5.js?externals=_local-default_:formatted:5
(anonymous) @ com.atlassian.plugins.atlassian-connect-plugin:iframe-host-utils-v5.js?externals=_local-default_:formatted:32
com.atlassian.plugins.atlassian-connect-plugin:content-resolver-v5.js?externals=_local-default_:1 Error running batched script.
com.atlassian.plugins.atlassian-connect-plugin:content-resolver-v5.js?externals=_local-default_:1 ReferenceError: _AP is not defined
at com.atlassian.plugins.atlassian-connect-plugin:content-resolver-v5.js?externals=_local-default_:5
WRMCB @ com.atlassian.plugins.atlassian-connect-plugin:content-resolver-v5.js?externals=_local-default_:1
(anonymous) @ com.atlassian.plugins.atlassian-connect-plugin:content-resolver-v5.js?externals=_local-default_:9
com.atlassian.plugins.atlassian-connect-plugin:module-loader-v5.js?externals=_local-default_:1 Error running batched script.
com.atlassian.plugins.atlassian-connect-plugin:module-loader-v5.js?externals=_local-default_:1 TypeError: Cannot read property 'awaitGlobal' of undefined
at com.atlassian.plugins.atlassian-connect-plugin:module-loader-v5.js?externals=_local-default_:5
WRMCB @ com.atlassian.plugins.atlassian-connect-plugin:module-loader-v5.js?externals=_local-default_:1
(anonymous) @ com.atlassian.plugins.atlassian-connect-plugin:module-loader-v5.js?externals=_local-default_:6
com.atlassian.plugins.atlassian-connect-plugin:iframe-host-js-v5.js?externals=_local-default_:1 Error running batched script.
com.atlassian.plugins.atlassian-connect-plugin:iframe-host-js-v5.js?externals=_local-default_:1 TypeError: Cannot read property 'awaitGlobal' of undefined
at com.atlassian.plugins.atlassian-connect-plugin:iframe-host-js-v5.js?externals=_local-default_:5
WRMCB @ com.atlassian.plugins.atlassian-connect-plugin:iframe-host-js-v5.js?externals=_local-default_:1
(anonymous) @ com.atlassian.plugins.atlassian-connect-plugin:iframe-host-js-v5.js?externals=_local-default_:7
com.atlassian.plugins.atlassian-connect-plugin:confluence-module-loader-v5.js?externals=_local-default_:1 Error running batched script.
com.atlassian.plugins.atlassian-connect-plugin:confluence-module-loader-v5.js?externals=_local-default_:1 TypeError: Cannot read property 'awaitGlobal' of undefined
at com.atlassian.plugins.atlassian-connect-plugin:confluence-module-loader-v5.js?externals=_local-default_:5
This is still very much a bug for me and my users.
Table Filter Macro fails to load tables built with the Jira Macro, even when only a few issues are returned.
It has never appeared to be fixed on my instance, for the simple use case I am leveraging the plugin for.
Hi akhaneev, yes this could be related to browser caches – I would suggest hard-reloading the page and seeing if the issue is still present. If it is, further reproduction steps on how your customers are running into this would be greatly appreciated.
Our customers still report this error: confluence/api/navigator-context missing confluence/api/querystring
Can it be related to browser caches? And is this fix rolled out to all Confluence instances?
Also I found this error
com.atlassian.plugins.atlassian-connect-plugin:ap-core-v5.js?externals=__local-default__:51 Uncaught TypeError: Cannot read property 'postMessage' of undefined at c (com.atlassian.plugins.atlassian-connect-plugin:ap-core-v5.js?externals=__local-default__:51) at XMLHttpRequest.f.onload (com.atlassian.plugins.atlassian-connect-plugin:ap-extensions-v5.js?externals=__local-default__:68) c @ com.atlassian.plugins.atlassian-connect-plugin:ap-core-v5.js?externals=__local-default__:51 f.onload @ com.atlassian.plugins.atlassian-connect-plugin:ap-extensions-v5.js?externals=__local-default__:68 load (async) request @ com.atlassian.plugins.atlassian-connect-plugin:ap-extensions-v5.js?externals=__local-default__:68 b._handleRequest @ com.atlassian.plugins.atlassian-connect-plugin:ap-core-v5.js?externals=__local-default__:53 c._receiveMessage @ com.atlassian.plugins.atlassian-connect-plugin:ap-core-v5.js?externals=__local-default__:65 react-beautiful-dnd.esm.js:5320 Uncaught ErrorEvent {isTrusted: true, message: "Script error.", filename: "", lineno: 0, colno: 0, …} onFatalError @ react-beautiful-dnd.esm.js:5320
Hello! I can now confirm that the more reliable fix has been released. I have verified that this fix works for Gliffy and Draw.io in production. Please kindly check and advise whether you still are seeing issues, and if so, what error messages you are seeing in the browser console.
The same error "confluence/api/navigator-context missing confluence/api/querystring" we see when using Table Filter and Charts app.
I've split off recent reports of `ReferenceError: _AP is not defined` into https://jira.atlassian.com/browse/CONFCLOUD-69391