Rider 2018.3.1 bug-fix update is here

Last week, we were in a hurry to deliver the first hotfix for Rider 2018.3 this year. And here it is! You are very welcome to download the Rider 2018.3.1 build right now.

Rider 2018.3.1 comes with fixes for:

  • Several issues in the debugger: RIDER-23087, RIDER-22932, RIDER-22770, RIDER-22887, and RIDER-22873.
  • Broken NuGet window after searching for “mongo” text (RIDER-22927).
  • Endless “Retrieving properties…” progress bar for Project Properties (RIDER-22924).
  • Inability to activate the dotTrace plugin via the License Server (RIDER-22876).
  • The “Failed to get the list of simulators” error on getting a list of iOS simulators (RIDER-22878).
  • The issue where a .jar setting file couldn’t be imported to Rider 2018.3 (RIDER-22823).
  • The misplaced position of inline parameter name hints (RIDER-22452).

There are several ways to get this hotfix:

  • Download and install from www.jetbrains.com.
  • Update right inside Rider: select Help | Check for updates.
  • Use our Toolbox App.
  • Use this snap package from the SnapCraft store if you are using a compatible Linux distro.
This entry was posted in How-To's and tagged , , , , , . Bookmark the permalink.

3 Responses to Rider 2018.3.1 bug-fix update is here

  1. Andreas Gullberg Larsen says:

    In 2018.3.1, rename-refactoring is excruciatingly slow on Unity projects. It seems to search a lot more files than before, such as lighting asset files (not source code).

    This is a regression from 2018.2. Not sure if I ever tested 2018.3, I’m on auto-upgrade.

    • Matt Ellis says:

      Since 2018.3, Rider will parse external Unity files such as scenes, assets and prefabs, looking for usages of e.g. methods used as event handlers. It seems that Rider isn’t narrowing down the search domain correctly during Find Usages, and is looking at some of these external Unity files when it shouldn’t, and is even including some files that shouldn’t be in the index at all. This has a more obvious impact in very large projects, and projects which contain some assets that have been forced as binary.

      I’ve raised RIDER-23266 to track this, and it should be addressed in 2018.3.2, due in a couple of weeks. As a workaround, you can disable parsing of text based assets in the Unity settings page (please remember to re-enable once 2018.3.2 is available!)

Leave a Reply

Your email address will not be published. Required fields are marked *