Apple Silicon (M1 chip) Support in Rider

Starting from Rider 2021.3 release, Rider runs natively on Apple silicon chips. Choose the ".dmg (Apple Silicon)" item in the Download selector on this page

Please note, that there is still no Rider for Unreal Engine build compatible with Apple Silicon. 

89 out of 96 found this helpful

Benjamintn .net5 working just fine here. Also .net 3


Much more fluent than the intel version! Thank you very much. Unfortunately when trying to connect a physical iPhone I get "The selected device was disconnected and cannot be accessed anymore from this machine". 

Edited by Felixlunzenfichter

Seems to be crashing on startup on latest Monterey beta 12

Translated Report (Full Report Below)

Process: rider [4791]
Path: /Applications/Rider
Identifier: com.jetbrains.rider
Version: 2021.2.1 (RD-212.5080.71)
Code Type: ARM-64 (Native)
Parent Process: launchd [1]
User ID: 501

Date/Time: 2021-09-02 16:12:41.3440 +0300
OS Version: macOS 12.0 (21A5506j)
Report Version: 12
Anonymous UUID: F445F755-947D-0DBA-E86D-FF9ABBF24E24

Sleep/Wake UUID: 974C79F9-4898-407A-BBDF-689FC99ECC1D

Time Awake Since Boot: 12000 seconds
Time Since Wake: 807 seconds

System Integrity Protection: enabled

Crashed Thread: 19 Java: JobScheduler FJ pool 0/7

Exception Codes: KERN_INVALID_ADDRESS at 0x0000100000bec000
Exception Codes: 0x0000000000000001, 0x0000100000bec000

VM Region Info: 0x100000bec000 is not in any region. Bytes after previous region: 17111162208257 Bytes before following region: 87960917721088
commpage (reserved) 1000000000-7000000000 [384.0G] ---/--- SM=NUL ...(unallocated)
---> GAP OF 0x5f9000000000 BYTES
MALLOC_NANO 600000000000-600008000000 [128.0M] rw-/rwx SM=PRV

Application Specific Information:
abort() called

Edited by Rahmanovdd

Rahmanovdd All jetbrains's products have this issue. You can view work around here mac os 12 beta6 Unable to start IDEA : JBR-3715 (


Rahmanovdd yeah, I see the same thing. It started with the newest beta of Monterey. The previous version worked fine.


Felixlunzenfichter Please report the connectivity issue to iPhone to the Thanks! 



I meant it was something generic like System or whatever that we already had a using directive for. Basically, We had a `class Foo` and it worked fine, then I guess they introduced a new class Foo in the System namespace in preview 7. Now the compiler wants me to decide which Foo this is.

Such an issue is not related to the SDK version Rider uses as runtime. There might be an issue in code analysis (ReSharper backend language server) since not all new languages features or changes are supported yet.  

So, if you still experience the issue, could you please try reproducing this in a demo solution and share it with us at


Alexander Kurakin Thanks for the clarification! Looking into it now.

BTW, this build is nearing its expiration date too if it is subject to 30 day expiration mentioned above :)


Hello, my laptop just died & I’m thinking of getting a new MacBook Pro M1 for work. Our codebase is still on .net 5. Will I be able to use this build or will I have to upgrade all the projects to .net 6? Thank you for your help.

Hi Benjamintn, I wouldn't rely on .net5 on m1 entirely yet since debugging doesn't work and when I try to test and work with .net6-rc1 ef commands doesn't work while .net5 (or any other .net core) is installed on the system. That being said, .net6 is in RC as I mentioned so it is very close and if you can update your project to .net6 (and have a little bit of time for it's final release) I would really recommend m1 laptops since they are really smooth. in-fact I'm writing this comment with an m1 air. I can though work with .net 4.7.2 or 4.8.x without any issues since mono is working fine for now/me.


Hi Jet Brains team! Yesterday I installed Rider for M1. Everything work perfect except 1 thing. 

I use postgres database in docker container and now I can't connect to it from Rider Database window. I got this error.

(561 ms)
I tried different drivers but nothing changed. 

Ekin, no, the latest available build shouldn't expire since it was build as part of the 2021.2.1 release chain. Please check JetBrains Rider | About JetBrains Rider dialog. There shouldn't be an expiration date. 



Alexander Kurakin I assume there'll be soon-ish a build based on RC1? Rider is probably the last piece in my "M1 puzzle" and the only one visibly slower than the same on my older generation Intel based device. Thanks for everything!


Thanks Rider team for all your effort! Could you post an update about .NET 6 RC1 build availability? I hope it will be more stable than the current one (it crashes more and more on my machine by an unknown reason).


So, I couldn't wait any more and installed the current build. What a difference!

Literally night and day, so happy to see this!

Thank you, thank you so much. Keep up the good work!


Hey everyone! 

We've just started the Rider 2021.3 EAP and Rider "Apple Silicon Edition" is included in it with patch updates, installation via the Toolbox, and .NET 6 RC1 as a runtime for the ReSharper backend. 



When I install Rider EAP from Toolbox, I get x64 version on my M1 MBP, not the aarch64 version.

Edited by Andrey

Alexander Kurakin please note somewhere that the toolbox still only suggests (without spelling it out) x64 version. Apple Silicon Edition must be installed manually. Not sure this is intentional.

Edited by Drazen Dotlic

Sorry for the trouble! We do have a problem with installation via the Toolbox app. We are working on a fix now. 



It's me once again. The Toolbox is fixed now, Rider "Apple Silicon Edition" is installed on the Apple Silicon machines. Apologies for the inconvenience. 


Can I target my app to use the same .NET6 RC1 as installed with latest Rider EAP for Apple M1 ?


For me the EAP 2021.3 M1 does not resolve some references. There is a lot of red in my Blazor solutions. I would like to keep working with 2021.2.1 M1 (Build 515.5080.71), if possible. Is that a problem?


Hello Matthew! No, it's not possible to use the .NET 6 SDK which Rider uses as the runtime for the backend.


Eluchsingerm you can still use 2021.2.1 M1 (Build 515.5080.71) if you want. You still can download it from if you lost the copy. 

By the way, could you please create a request here with more details about the problem you experienced with EAP build? We will much appreciate that. Thanks! 



Alexander Kurakin please update a new version. Thank you


Has anyone experienced really slow performance when running XUnit tests ?

Running tests on Rider 2021.3 EAP4 on Apple M1 mbp set of tests take ~2 min 30 secs.

But running the same code and tests on an Intel x86 mbp, the same set of tests takes ~ 30 secs

This perf issue makes running Xunit tests locally a huge blocker to following best practice.

regards Matt


Guys, I am about to buy new laptop and need your honest opinion. I am considering MBP M1 (been using windows laptops up to now).

Is this thing ready/usable? I expect it to be buggy at this stage, but is it usable with some workarounds?




Rider has been my main tool for Xamarin development in MBA M1. 
It's actually slower than intel based macs for now as it takes longer to build iOS and Android apps. However I have no other complains. It just works. 
Though I can't tell about or .net5/6 as I haven't used for that yet. 



Most limitations are related to dotnet stack, not to the Jetbrains toolchain.

I don't know how to work with dotNet classic projects for example. It is restricted to both intel and windows. Not sure is it even possible to run x64 virtualized windows on M1 right now. Bootcamp is also unavailable afaik. I just use remote Windows for this, but maybe there are better solutions.

As for Rider issues atm. I failed to find how do I use GUI version of dotMemory, dotTrace and so on on my Mac. Debugging is much less stable on mac version, but still is ok. Annoying message with SSL certificate every Rider launch of net core project. Nothing really critical here, especially when I have an access to Windows PC. Also it become better and better each month. 

dotnet stack has alot more issues. Like you can't mix x64 and native sdks at the same time. They corrupt each other. The only native version available is .Net 6 RC (stable will be in November). If you use it, you can't use .Net 5 or 3.1 and vice versa. X64 works slow, even compiler is really slow. Native is great in most cases, but it still in RC state and I am getting some weird bugs all the time. Like ConcurrentQueue.ToImmutableArray() crashes in current RC (it takes count and then enumerates and expects it to have exactly that count of items). 


Andrey, you can use it .NET5(x64) and .NET6(arm) both on Mac.

Unpack .net5(x64) in /usr/local/share/dotnet/x64

Unpack .net6(arm) in /usr/local/share/dotnet


For run/debug projects:

Add env DOTNET_ROOT=/usr/local/share/dotnet/x64 in your Launch Profile .NET5 projects in Rider

For run/debug unit tests (obj/bin folders must be deleted before build once):

Add\Edit Directory.Build.props in your .NET5 project(s)


Please sign in to leave a comment.

Have more questions?

Submit a request