Search Issue Tracker
Won't Fix
Votes
0
Found in
2020.1.0a19
2020.2.0a2
Issue ID
1226343
Regression
Yes
[Asset Importers] Unity doesn't re-create missing launcher files in the Library folder
.npm, node and null files do not recreate while launching Unity for the first time.
Steps to Reproduce:
1. Get a PC which didn't have Unity installed or delete three files -.npm, node and null, located in
For macOS: Library/Unity/Packages(package.js should be left)
For Windows: AppData\Roaming\Unity\Packages
2. Install Unity 2020.2.0a3.
3. Start Unity.
Actual Result:
.npm, node and null files not created.
Expected Result:
Without any issues .npm, node and null files are recreated.
Occurring on:
2020.2.0a3, 2020.1.0b1, 2020.1.0a19.
Working Fine on:
2020.1.0a18
Environment:
Windows 10 & macOS 10.14
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
- var VisionOSEDRHeadromm has a comma instead of a dot when building with Metal Rendering App Mode and local OS localization is set to German
- IAP Catalog remove product “x” and add product “+” buttons are not consistent with other remove and add buttons in the Editor
- Performance issues in Play Mode when quickly hovering the mouse cursor over Hierarchy GameObjects
- Frame Debugger displays incorrect output when FidelityFX Super Resolution or Spatial-Temporal Upscaler is used with Temporal Anti-aliasing or Subpixel Morphological Anti-aliasing
- The layout system is failing to correctly calculate or apply the height of the Japanese fallback font when the primary English font's metrics are used
Resolution Note (2020.2.X):
Since the CEF removal we do not create javascript packages anymore. Whoever needs these .npm files need to take ownership of them.