Search Issue Tracker

Active

Under Consideration for 6000.0.X, 6000.2.X, 6000.3.X, 6000.4.X

Votes

4

Found in

6000.0.58f1

6000.2.6f1

6000.3.0b3

6000.4.0a1

Issue ID

UUM-119499

Regression

No

Getting a deprecated package for JetBrains Rider pop up when opening or creating a project

-

Steps to reproduce:
1. Open an exisiting project or create a new project on any version of Unity

Actual results:
Getting a Package Manager pop up for deprecated JetBrains Rider

Warning message in the pop up:
"This project contains one or more packages with errors. Do you want to open Package Manager?"

Error message in the PM window:
"3.3.0.37 has a regression: newly created C# files are not added in the project"

Expected results:
Package is updated or correct version is used while creating a new project

Reproducible with versions:
6000.0.58f1, 6000.2.6f1, 6000.3.0b2, 6000.3.0b3, 6000.4.0a1

Not reproducible with versions: 
6000.3.0b1, 6000.3.0b4

Tested on (OS):
MacOS Sequoia 15.6.1

Notes:

  • Updating or removing the package still give the pop up when creating a new project

Comments (5)

  1. MartinWorker

    Oct 11, 2025 19:29

    The problem is still exists in 6000.2.6f2.
    Reproduce:
    1. make a local HDRP project
    2. open it.
    3. enjoy the popup

  2. nlp_eschipellite

    Oct 07, 2025 14:45

    Noticed on the latest 6000.0.58f1 and 6000.0.58f2.

    While this isn't a huge issue (since you can just manually updated the deprecated package), it does annoyingly occur whenever your first create a new project within these versions.

    Hopefully this is updated on the version-side for the next LTS update in the upcoming weeks.

  3. 99crusader

    Oct 04, 2025 19:16

    Due to the security risk, I updated my project from 6000.0.38 to 6000.0.58 and encountered this error as well. Since I do not use any JetBrains products, I removed the package. However, in doing this, I was getting a host of Unity Editor errors where components would just stop loading text and I was getting GetName errors. I reinstalled the package (thus upgrading the new version) and I'm no longer getting the errors. Not sure why this package has to be installed if I'm not using Rider.

  4. kantagara

    Sep 19, 2025 12:16

    Seems to be solved by upgrading to .38 version of the plugin

  5. kantagara

    Sep 19, 2025 12:13

    Same thing happens on Windows

Add comment

Log in to post comment

All about bugs

View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.