Search Issue Tracker

Fixed in 2020.1.X

Fixed in 2019.4.X

Votes

0

Found in

2018.4

2019.3

2019.3.13f1

2020.1

Issue ID

1255051

Regression

No

[AssetPipelineV2] Package status is not correctly reflected upon loading the project when the package is disabled externally

Asset - Database

-

How to reproduce:
1. Download the user-submitted project (PackageModStausADBv2.zip)
2. Before opening, check that the Packages/manifest.json file does not contain "com.unity.modules.cloth": "1.0.0"
3. Open the project, see the Package Manager built-in modules that Cloth is disabled
4. Check the Console window/enter the Play Mode in SampleScene

Expected result: Test.cs script throws errors due to disabled Cloth module, Play Mode cannot be entered
Actual result: no errors are thrown, Play Mode can be entered and Cloth still works

Reproducible with: 2018.4.23f1, 2019.4.1f1, 2020.1.0a21
Not reproducible with: 2020.1.0a22, 2020.1.0b13, 2020.2.0a15

Notes:
2018.4 reproduces the issue with ADBV1, but reimporting the script starts displaying the errors
2019.3 and newer do not reproduce the issue with ADBV1; with ADBV2 the scripts still do not start displaying errors when reimported

  1. Resolution Note (fix version 2020.1):

    Fixed in 2020.1.0a22

  2. Resolution Note (fix version 2019.4):

    Fixed in 2019.4.4f1

Log in to vote on this issue

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.

Latest issues

See all new issues