Install Rider on macOS *WITHOUT* stealing all my file extension associations?

Hello,

I'd very much like to use Rider on macOS. Without asking me at all, it took over any developer related file extension associations. First, that's not nice. Secondly, the aesthetic of the JetBrains icons in Finder is, in my opinion, not pleasing.  So much so, I spent the last hour removing all traces of Rider, restoring .plists from backups, and the like. Before the nuclear option, attempting to remove extension associations from the Rider settings, but that didn't do anything,

It's one thing for a word processor to associate with one or two extensions, but Rider taking over for everything breaks my usage. (I use `open` from the command line constantly).

Is there a way to install Rider so it doesn't associate with ANY files? 

0
1 comment

Hello John, 

Thanks for contacting Rider support. Based on my test, installing Rider in macos shouldn't change the file type association. 

Could you reproduce the issue and use the following way to identify which process changed the file type association:

1. To simplify the process, let's focus on one file type, e.g. *.sln. Before reporducing the issue, change the file type association to another app, such as Text Editor. 

2. In macos terminal, run log stream --predicate 'process == "lsd"' --info 

3. Install Rider and reproduce the issue. Observe the output of “log stream” command. When a file type association is changed, you should see the output like below:

2026-08-11 15:08:17.704500+0800 0x347d34b  Default     0x32d6144            650    2    lsd: (LaunchServices) [com.apple.launchservices:default] pid 954 setting handler for content type dyn.ah62d4rv4ge81g5ds roles ffffffff to <private> v (null) -> 0

Identify the process:

In this example, pid 954 is the PID of the process which makes the change. 

ps aux | awk 'NR==1 || $2==954'

If it's already gone, check the logs:

log show --predicate 'processID == 954' --last 1h | head -20

If there're many similar output, you can also run mdls -name kMDItemContentType /file/path/to/sln/file to check content type of the sln file(dyn.ah62d4rv4ge81g5ds in this case), then filter the output accordingly. 

Next Action:

If still no clude or it's confirmed the issue is indeed caused by Rider, please provide the following information:
1. How did you install Rider, via Toolbox app or standalone installer?

2. Provide a few samples of file types affected by this, e.g. *.cs, *.sln

3. Share the output of log stream, and your findings. You can upload the output in our Upload Service and share the Upload ID.

Please let me know if you have any questions. 

 

Thanks,

Tom

 

0

Please sign in to leave a comment.