Apple Silicon (M1 chip) Support in Rider

Starting from 2021.3 EAP, the Apple Silicon support is included in the regular Rider and will be delivered as part of our EAP and release pipelines. The EAP builds use the following runtimes:

  • The Apple silicon–compatible JBR (JetBrains Runtime) for the frontend.
  • The .NET6 RC1 for the backend.

You can download the Rider 2021.3 EAP from this page (select ".dmg (macOS Apple Silicon)" item for the Download button) or via the JetBrains Toolbox app.

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

56 comments
Comment actions Permalink

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

2
Comment actions Permalink

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
0
Comment actions Permalink

Seems to be crashing on startup on latest Monterey beta 12




-------------------------------------
Translated Report (Full Report Below)
-------------------------------------

Process: rider [4791]
Path: /Applications/Rider ARM.app/Contents/MacOS/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 Type: EXC_BAD_ACCESS (SIGABRT)
Exception Codes: KERN_INVALID_ADDRESS at 0x0000100000bec000
Exception Codes: 0x0000000000000001, 0x0000100000bec000
Exception Note: EXC_CORPSE_NOTIFY

VM Region Info: 0x100000bec000 is not in any region. Bytes after previous region: 17111162208257 Bytes before following region: 87960917721088
REGION TYPE START - END [ VSIZE] PRT/MAX SHRMOD REGION DETAIL
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
0
Comment actions Permalink

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

0
Comment actions Permalink

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

0
Comment actions Permalink

Felixlunzenfichter Please report the connectivity issue to iPhone to the https://youtrack.jetbrains.com/issues/RIDER. Thanks! 

0
Comment actions Permalink

Ekin 

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 https://youtrack.jetbrains.com/issues/RIDER?

0
Comment actions Permalink

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 :)

0
Comment actions Permalink

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.

0
Comment actions Permalink

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.

com.intellij.execution.ExecutionException.
(561 ms)
 
I tried different drivers but nothing changed. 
0
Comment actions Permalink

Dmitriy Grebennikov Please file a new request here.

Thanks! 

0
Comment actions Permalink

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. 

Thanks! 

0
Comment actions Permalink

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!

1
Comment actions Permalink

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).

2
Comment actions Permalink

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!

2
Comment actions Permalink

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. 

Thanks! 

2
Comment actions Permalink

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

Edited by Andrey
0
Comment actions Permalink

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
0
Comment actions Permalink

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

 

1
Comment actions Permalink

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. 

1
Comment actions Permalink

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

0
Comment actions Permalink

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?

0
Comment actions Permalink

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

0
Comment actions Permalink

Eluchsingerm you can still use 2021.2.1 M1 (Build 515.5080.71) if you want. You still can download it from https://download.jetbrains.com/rider/JetBrains.Rider-2021.2.1-aarch64.dmg if you lost the copy. 

By the way, could you please create a request here https://youtrack.jetbrains.com/issues/RIDER with more details about the problem you experienced with EAP build? We will much appreciate that. Thanks! 

 

0
Comment actions Permalink

Alexander Kurakin please update a new version. Thank you

1
Comment actions Permalink

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

0

Please sign in to leave a comment.

Have more questions?

Submit a request