Search Issue Tracker
By Design
Votes
2
Found in
6000.2.3f1
6000.3.0b1
6000.4.0a1
Issue ID
UUM-117265
Regression
Yes
“Failed to parse data …“ and “Invalid Script reference …” errors appear in the Console when importing specific assets
How to reproduce:
1. Create a new project
2. Drag and drop into /Assets the custom package: “IN-112289_ModelBug.unitypackage”
3. When prompted to import the package, click “Import”
4. Observe the Console
Expected result: No errors appear in the Console
Actual result: “Failed to parse data …“ and “Invalid Script reference …” errors are shown in the Console
Reproducible with: 6000.2.0a10, 6000.2.3f1, 6000.3.0b1 (fcdf07aae9b4)
Not reproducible with: 6000.0.57f1, 6000.2.0a7
Could not test with: 6000.2.0a8, 6000.2.0a9 (crashes instead)
Reproducible on: Windows 11
Not reproducible on: No other environments tested
Notes:
- To see if the errors appear, remove the package (Assets/MODELS) and re-open the project
- The errors do not appear if the project already has the package assets imported
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:
Thank you for reporting a bug to Unity.
The error messages are due to a defective asset. We are contacting the asset author so they can make appropriate changes. We are also investigating on how to improve the Asset Store validation pipeline.
Today we will be closing this case. Thank you again for taking the time to report this issue, and please let us know if there is anything else that changes the impact or severity of this issue.