Search Issue Tracker
Not Reproducible
Votes
0
Found in
2019.4
2019.4.8f1
2020.2
Issue ID
1273517
Regression
Yes
[V1 - V2 Regression] The mainObjectFileID value is not set when creating an Asset
How to reproduce:
1. Open user's attached "mainObjectFileID test - 2019.4.8f1" project
2. Create a "MyMaterial" Material by going to Tests->Create asset->Material
3. Right-click on the "MyMaterial" Material and press "Show In Explorer" ("MyMaterial" is found in the Assets->Test assets folder)
4. When the folder opens, open the "MyMaterial.mat.meta" with a text editor
Expected result: The mainObjectFileID value is 2100000
Actual result: The mainObjectFileID value is 0
Reproducible with: 2019.3.0a1, 2019.4.9f1, 2020.1.4f1, 2020.2.0b1
Could not test with: 2018.4.27f1 because the Asset Import Pipeline Version 2 was not yet introduced
Notes:
- The issue is reproducible only with Asset Import Pipeline Version 2
- The issue is reproducible with any created Asset
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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Resolution Note (2019.4.X):
Verified fixed on 2019.4.33f1, 2020.3.22f1, 2021.2.1f1