Search Issue Tracker
Fixed in 2018.4.X
Fixed in 2017.4.X, 2019.1.X, 2019.2.X
Votes
0
Found in
2017.4.0f1
2018.3.3f1
2018.3.6f1
2019.1.0a1
2019.2.0a5
Issue ID
1126293
Regression
No
Editor does not react to .meta file changes regarding Asset Bundles when .meta file was changed while the Editor was closed
How to reproduce:
1. Create a new project
2. In the Hierarchy create an empty Game Object
3. Drag it to the Project window to make it a prefab
4. Right-click the prefab and select show in explorer
5. Copy the GameObject.prefab.meta file to another folder
6. Select the Prefab and create a new AssetBundle for it
7. Exit Unity
8. Copy the GameObject.prefab.meta file from another folder to the Assets folder
9. Launch the project again and select the Game Object prefab
Expected result: Game Object is not in an Asset Bundle
Actual result: Game Object is in an Asset Bundle
Reproducible with 5.6.6f2, 2017.4.20f2, 2018.3.6f1, 2019.1.0b3, 2019.2.0a5
Fixed in: 2017.4.32f1, 2018.4.2f1, 2019.1.5f1, 2019.2.0a12, 2019.3.0a2
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Long Prefab save times when using Unity 2022.2 and higher
- Console displays error "UnityException: Creating asset at path Assets/Scenes/ .scenetemplate failed." during scene template saving
- "Development Build" watermark is shown in non-development UWP release builds
- Console errors appear when the Inspector is set to Debug and a GameObject is selected
- A script public variable value is not used when set in the Inspector window
Add comment