Can no longer execute C# binaries on macOS Sequoia 15.3
I have been using Visual Studio Code to build and run C# code on macOS for quite a while but am suddenly having issues with it where the executable just “does nothing”. i.e. you create a basic “Hello World” Console.WriteLine app, it builds successfully, but when you run it there's no output - just nothing happens.
Having used Rider in the past, I thought I'd quickly download the commercial-free version and see what happens there. I'm finding similar problems occurring - create the default Console App (which just does a Console.WriteLine) and build and run it. In the case of Rider though, I see the following error:
Process finished with exit code 137.
For which I can't find anything speciifc related to macOS/C#/Rider.
I suspect there's something going on with a macOS update that's broken .NET somehow.
If someone else is running macOS Sequoia 15.3 and Rider, can you try build and run on the basic Console App and see if you're having any issues?
Please sign in to leave a comment.
Rider has the similar implementation with
dotnet CLI. Exit code 137 points to a memory issue, but it could also not be the root cause.What's the
dotnet runresult in the system terminal? Use the-vflag to specify the log level to see if it could provide further information.Sorry - when I said above “i.e. you create a basic “Hello World” Console.WriteLine app, it builds successfully, but when you run it there's no output - just nothing happens.” I was referring to the Terminal. See screenshot.
I'm mostly looking for the below - i.e. someone to confirm they DON'T have the issue using macOS Sequoia 15.3, as that upgrade is what seems to have broken things for me.
If someone else is running macOS Sequoia 15.3 and Rider, can you try build and run on the basic Console App and see if you're having any issues?
Could you repost the screenshot? Any differences between the Rider integrated terminal and the system terminal?
I'm running MacOS Sequoia 15.3 and just updated to 15.3.1. Console apps work fine, as do webapps.
All good. I've figured out that the problem is due to a sneaky deployment of Airlock onto the company laptops that suddenly preventing all unsigned executables from running.