Atlassian Macro Library throwing an error on Macro opening in Confluence

Question

When trying to open our macro that uses a modal for configuration, we see an unknown error from Atlassian macro library:

com.atlassian.plugins.atlassian-connect-plugin:confluence-macro-v5.js?assetVersion=1000.0.0-7b3b4190df0119827&externals=__local-default__:10 Uncaught (in promise) TypeError: Cannot read properties of undefined (reading 'getEditor')
   at Object.openCustomEditor (com.atlassian.plugins.atlassian-connect-plugin:confluence-macro-v5.js?assetVersion=1000.0.0-7b3b4190df0119827&externals=__local-default__:10:483)
   at opener (com.atlassian.plugins.atlassian-connect-plugin:macro-editor-resources-v5.js?assetVersion=1000.0.0-7b3b4190df0119827&externals=__local-default__:20:430)
   at a.open (com.atlassian.confluence.plugins.confluence-macro-browser:macro-browser-js.js?assetVersion=1000.0.0-7b3b4190df0119827&externals=__local-default__&locale=en-US:134:447)
   at index.ts:585:4

The issue happens for a specific tenant in production environment

Marcus Heino · Answer

Thanks @Roma Bubyakin _Wombats Corp_ ,

Well, today looks much better and everything is working without any errors! I did not do any actions in order to "fix" it.

For Chrome I actually did clear the browser cache this morning (due to another reason) but for Edge I did not do anything and it works on both browsers so I don't even think it was related to the browser cache. Maybe yesterday was just not my day or Atlassian had indeed done some small fix in the background as suggested by @Lauma Cīrule .

Have a good day, all!

Roma Bubyakin _Wombats Corp_ · Answer

Wow!
I have to admit that you faced quite an interesting issue.

Unfortunately, I'm not able to help you with the solution. However, I can share my assumptions that might help with further actions.

1. It's a Confluence issue (not an app-related one). Based on the error message.
2. Account-level problem (not cookies or other browser cache). As only you faced it, and changing the browser doesn't help.

You may create a ticket to Atlassian (which is always good and mostly helpless).

Also, you may proceed with investigations on your own.
I would recommend that you:

* Check permissions of any kind
* Compare account settings with your colleagues
* Look into your user properties

I wish you to solve it, and looking forward to the happy end of the story.

Regards,
Roman from Wombats Corp

Lauma Cīrule · Answer

Hi,

I am Lauma from eazyBI team. We noticed the same issue on one of our test sites earlier today, but Atlassian promptly resolved it.

I cannot confirm if the resolution was site-specific, so if the issue persists, I recommend contacting Atlassian Support directly. You're also welcome to copy support@eazybi.com if you need any additional assistance from our side.

Hope it gets resolved for you soon!

Lauma / support@eazybi.com