Search Issue Tracker

Fixed

Fixed in 6000.0.76f1, 6000.3.16f1, 6000.5.0b9, 6000.6.0a5

Won't Fix in 6000.4.X

Votes

0

Found in

6000.0.64f1

6000.3.1f1

6000.4.0b1

6000.5.0a3

6000.6.0a1

Issue ID

UUM-129833

Regression

Yes

Local package MonoBehaviour scripts appear as missing after updating the project when the project and package paths share the same prefix

Scripting Buildtime

-

How to reproduce:
1. Open the attached “Viewer” project (in “IN-124519_Upgrade bug.zip”)
2. Open “SampleScene“
3. Enter Play mode
4. Observe the Console window

Expected result: The custom warning messages appear: “Some script has started” and “Some other script has started”
Actual result: The Unity Editor warning messages appear: “The referenced script (Unknown) on this Behaviour is missing!”

Reproducible with: 2023.2.0a19, 6000.0.64f1, 6000.3.1f1, 6000.4.0b1, 6000.5.0a3
Not reproducible with: 2023.2.0a16
Could not test with: 2023.2.0a17, 2023.2.0a18 (Crash on _platform_memmove when opening the project)

Reproducible on: macOS 15.3.2 (24D81) (M1 Max)
Not reproducible on: No other environments tested

Notes:

  • Removing the “Library” folder after updating the project does not resolve the issue
  • The bug is not reproducible with the following local package paths:

{{"file:../../aViewerShared/com.revizto.revizto-shared"}}

{{"file:../../Unity6000-ViewerShared/com.revizto.revizto-shared"}}

{{"file:../../SharedPackages/com.revizto.revizto-shared"}}

{{"file:../../SharedPackages/ViewerShared/com.revizto.revizto-shared"}}

  • And reproducible with these local package paths:

{{"file:../../ViewerPackages/com.revizto.revizto-shared"}}

{{"file:../../ViewerShared/com.revizto.revizto-shared"}}

  1. Resolution Note:

    Fixed in 6000.6.0a5

  2. Resolution Note (fix version 6000.6.0a5):

    Fixed in 6000.6.0a5

  3. Resolution Note (fix version 6000.5.0b9):

    Fixed in 6000.5.0b9

  4. Resolution Note (6000.4.X):

    The fix was not ported to 6.4, but to 6.3 and 6.5 instead

  5. Resolution Note (fix version 6000.3.16f1):

    Fixed a bug where String.Replace() was incorrectly stripping project names from package paths when the project name was a prefix of the package path.

  6. Resolution Note (fix version 6000.0.76f1):

    Fixed a bug where String.Replace() was incorrectly stripping project names from package paths when the project name was a prefix of the package path.

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.