Studio Pro 11.9.1 on MacOS 14 - Modelling Editors dont open

0
My colleague uses a MacBook Air M1 with MacOS 14 for development. Studio Pro can be installed and started, but after creating a new app the main editor section shows the following error message:API with ID 'mendix.ApiAccessApi' does not exist locally and no remote provider was discovered within the configured timeoutPlease close and reopen this Ul component. If the issue persists, contact Mendix Support v Details@http://localhost:49883/component/component-framework/main.js:1:49948Looking at the log file shows the following problems:2026-04-22 09:18:09.1949 INFO Mendix.Modeler.Controls.WebBrowser.MacOS.WKWebViewWebBrowserHandler Created mac WebView2026-04-22 09:18:09.7074 ERROR lambda_method353 There was no listener registered for channel 'mendix.AppLanguageSettingsApi' within the specified timeout. See details for more information. - Studio Pro tried sending message 'activeLanguageChanged' to a component using channel mendix.AppLanguageSettingsApi. It has been more than 60 seconds since the first message has been sent to the same channel. However, the component has still not sent the MessageListenerRegistered message, which notifies Studio Pro that a listener for this channel has been registered. This usually results in a memory leak (as undelivered messages are getting queued), forcing us to close the channel until MessageListenerRegistered is received. But, it can also indicate that message listener gets registered late in the component lifecycle, while Studio Pro tries sending messages in the meantime. Please make sure that your component registers message listeners as soon as possible.That might be a timing issues because the MacBook is too slow. Some editors (property sidebar) work. Any ideas?
asked
1 answers
0

Hi Martin,

I don't think an M1 MacBook Air is simply "too slow" for Studio Pro. The error messages look more like a startup/communication problem between Studio Pro and the embedded UI components than a performance bottleneck.

The key clues are:


Plain Text



API with ID 'mendix.ApiAccessApi' does not exist locally

and


Plain Text



There was no listener registered for channel

'mendix.AppLanguageSettingsApi'

These suggest that one or more editor components are failing to initialize and therefore never register their API channels with Studio Pro.

A few things I would try:

  1. Delete local Studio Pro caches/settings
  2. On macOS, clear the Studio Pro local data/cache directories and start Studio Pro again.
  3. Test on a newly created blank app
  4. Since you mentioned the issue occurs immediately after creating a new app, confirm whether:
    • Every new app fails.
    • Only a specific project fails.
  5. If a completely new app shows the same behavior, the problem is likely the Studio Pro installation rather than the project.
  6. Check WebView installation
  7. The log contains:
  9. Plain Text
  12. WKWebViewWebBrowserHandler
  13. Created mac WebView
  15. The modeling editors on macOS rely heavily on embedded web-based components. If the WebView environment is corrupted or blocked, editors may never finish loading and therefore never register their APIs.
  16. Upgrade Studio Pro
  17. If possible, test with a newer Studio Pro version than 11.9.1. Since macOS support is still evolving, I've seen issues disappear in later releases without any project changes.
  18. Check security software
  19. Corporate endpoint protection, VPN software, content filters, or browser-security tools can occasionally interfere with localhost communication such as:
  21. Plain Text
  24. http://localhost:49883
  25. which is exactly what your error references.
  26. Review the Studio Pro log for the first error
  27. Often the listener-registration errors are secondary. There may be an exception earlier in the log indicating why the component failed to start in the first place.

My suspicion is that a web component fails during initialization, causing:


Plain Text



ApiAccessApi missing

↓

listener never registered

↓

modeling editors never open

rather than the machine being underpowered. An M1 Air should be more than capable of opening the editors.

If all newly created apps exhibit the same behavior, I'd strongly consider opening a Mendix Support ticket and attaching the Studio Pro log, as this looks like a Studio Pro for macOS issue rather than a project-specific configuration problem.



answered