Does this mean you are creating your own nested iframe inside your Connect app iframe? If so, loading the all.js library in that nested iframe won’t work without taking extra measures.
I believe Atlassian is using their simple-xdm library to implement AP / all.js functionality. You could either look into setting that up for your nested iframe as well or use other means of communication between your nested iframe and parent iframe, and have your parent iframe delegate calls to AP.
After some experiment, I am coming to this conclusion
AP.context.getContext always returns empty object inside custom macro editor. It seems the getContext is not supported inside custom macro editor.
If you call multiple atlassian APIs in parallel from connect JavaScript library then you many not receive the callback for some of the APIs. However if you call them serially then your callbacks get called always. In the above example, if I chain the API calls then I get the callbacks always but when done in the parallel (as in my first post in this thread) then randomly some of the callbacks are not called back.
@ibuchanan
I would like someone from Atlassian to confirm this behavior as expected behavior. I do not find these anywhere in the documentation.