Help reproducing weird MacOS Aarch64 system error maybe caused by gradle issue

Started by Omegabird113 on

Topic category: Troubleshooting, bugs, and solutions

Joined Jul 2023
Points:

User statistics:

  • Modifications:
  • Forum topics:
  • Wiki pages:
  • MCreator plugins:
  • Comments:
Help reproducing weird MacOS Aarch64 system error maybe caused by gradle issue
Sun, 03/15/2026 - 22:18 (edited)

So, I’ve been having a bug that’s been bothering me. I’d report on the issue tracker, but I have no way to reproduce it, it just happens. This has only ever happened on sense I got my M4 Mac Mini (MacOS 15.3 at start, MacOS 26.3.1 now) since MCreator 2024.4 all the way including my 2026.1 dev environment while working on PR #6125.

The issue:

I load into MCreator (shortly after waking my Mac from sleep after using MCreator earlier, closing the app, and putting my Mac to sleep, this is a pattern for a lot of the time it happens), try to run the client, and get the following error: Failure on line 688 in function id scheduleApplicationNotification(LSNotificationCode, NSWorkspaceNotificationCenter *): noErr == _LSModifyNotification(notificationID, 1, &code, 0, NULL, NULL, NULL).

I can fix it by deleting the ~/.mcreator/gradle folder. However, if I save that folder before deleting it and restore what should be the broken version, it does not cause the bug to reappear. Same goes if I also add the workspace gradle, .gradle, and build folders. To me, this means that resetting gradle must trigger something somewhere else to fix itself.

When this bug happens, it effects all my workspaces. Clearing the gradle cache folder within MCreator doesn’t work either.

I have no ability to trigger this bug to occur. It tends to happen about every month or so in a burst of 2 (as in it tends to happen a second time within a week or so of the first, then it settles for a while).
 

I understand if there’s not much that can be done about it because of the weirdness and inability to reproduce. As it happens again to me, I’ll try to add more documentation. 

Edited by Omegabird113 on Sun, 03/15/2026 - 22:18
This is most likely a Gradle…
Mon, 03/16/2026 - 14:43

This is most likely a Gradle or NeoForge bug or even MC in Gradle env bug

I have also seen this from other sources:

Apple has had regressions in these areas around sleep/wake cycles in newer macOS versions.

Joined Jul 2023
Points:

User statistics:

  • Modifications:
  • Forum topics:
  • Wiki pages:
  • MCreator plugins:
  • Comments:
My current theory is that it…
Mon, 03/16/2026 - 14:52

My current theory is that it’s a MacOS sleep bug interacting with the gradle daemon and putting either the daemon or the system in a corrupted state,