Search Issue Tracker
Won't Fix
Votes
0
Found in
2018.4
2019.3.1f1
2020.2
Issue ID
1220938
Regression
No
Package Version defines are not updated/re-evaluated when modifying the package.json manifest
Reproduction steps:
1. Open the attached project ("case_1220938-FailedReimport")
2. Open the repro scene ("VersionDefineTest")
3. In Hierarchy, select "VersionDefineTest" object
4. In Inspector, notice that public "VersionDefineIsWorking" variable is visible
5. In the Project tab, select "Packages/NMY Core/package.json"
6. Change the selected manifest's "Version" to "0.9.0-b"
7. Select the same "VersionDefineTest" object in the Hierarchy
Expected result: Version defines are updated and "VersionDefineIsWorking" variable is no longer visible
Actual result: Version defines are not updated and "VersionDefineIsWorking" variable is still visible
Reproducible with: 2018.4.18f1, 2019.3.6f1, 2020.1.0b2, 2020.2.0a3
Couldn't test with 2017.4 (Packman not supported)
Notes:
1. In very rare cases, the issue does not reproduce from the first attempt. In the repro project, setting "Version" back to "0.9.0-d" always reproduces the issue (the variable does not appear again)
2. Reimporting the "NMY Core" package fixes the issue
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Search field in UI Builder's Library has no character limit
- Changing the value in UI Builder by dragging increases it by a few thousand points when reaching the borders of the screen
- ARM64 architecture DLL incorrectly copied instead of x64 when building for Windows x64
- Crash on TypeTreeIterator::GetNode when opening a specific folder
- Crash on WriteSerializedAssetsV2 when (re)entering the Play Mode in a specific project when IEnumerator Start() is used
Resolution Note:
Since the modification is not done to a script, a recompile is not triggered. A reimport of the package using the modified value is necessary to use it properly.