I install the SMAPI, and when I will run the game, have this error and the SMAPI archive is moved to trash. Im using MacOS Sequoia 15.1.1

SMAPI Log.

Last login: Thu Nov 28 17:15:36 on ttys003
guilherme@Guilhermes-MacBook-Pro ~ % /Users/guilherme/Library/Application\ Support/Steam/steamapps/common/Stardew\ Valley/Contents/MacOS/StardewModdingAPI ; exit;
zsh: killed

Saving session...
...copying shared history...
...saving history...truncating history files...
...completed.

[Process completed]

Hi! Installing the latest SMAPI 4.1.8 (just released today) should fix compatibility with the new macOS security restrictions. If you still need help, feel free to ask on the mod page instead!

macOS Ventura here, it took me two and a half hours to finally confirm the game won’t run with smapi installed, and I have updated to the latest 4.1.8. Tried everything with disabling gatekeeper, removing any com.apple.quarantine xattr, entering safe mode then deleting any unwanted plots… there is still the popup saying the file is broken, it will harm your system blablabla, the only difference with this posted issue is that it does not say malicious, but the file is downloaded at an unknown date. I don’t know what to do now. The game and smapi was uninstalled and reinstalled many times, tried every combination I can think of.

macOS M2 Sonoma 14.5

Logs:
/tmp/open-smapi-terminal.command ; exit;
/Users/chen/Library/Application Support/Steam/steamapps/common/Stardew Valley/Contents/MacOS/StardewValley: line 196: 50812 Killed: 9 ./StardewModdingAPI "$@"

Saving session...completed.

Edit:
discord
When I install 4.1.7 and run the following code in the terminal, it works.
codesign --force --sign - "Library/Application Support/Steam/steamapps/common/Stardew Valley/Contents/MacOS/StardewModdingAPI"

Hi @Pathoschild , I attempted to install SMAPI 4.1.8 fresh on Stardew Valley on Mac running Sequoia 15.1.1 today, received warning:

EDIT : The stardewvalley Discord has a megathread for troubleshooting this issue, including a workaround with involves installing 4.1.7 (which worked for me!)