Search Issue Tracker
Fixed in 2020.1
Fixed in 2019.3
Votes
0
Found in
2019.3.0a1
2019.3.0f6
2020.1
Issue ID
1217774
Regression
Yes
Calling AssetDatabase.ImportAsset() on a prefab, while having a reference to the prefab objects, breaks the references
How to reproduce:
1. Open the attached project
2. Go to top toolbar's BugTest->ScriptableObject Reference Test
3. Drag SOTest Asset to "ScriptableObjectLoader" Scriptable Object's field
4. Inspect the entries
5. Reimport one of the following, "Cube" or "Cube 1" in Assets
6. Inspect the entries again
Expected result: Entries for the reimported Prefab are not changed
Actual result: Entries for the reimported Prefab are null
Reproducible with: 2019.3.0a1, 2019.3.1f1, 2020.1.0a23
Not reproducible with: 2017.4.37f1, 2018.4.17f1, 2019.2.21f1
-
ainsley987
Feb 09, 2020 14:19
You must check this post on MetroPCS Coverage Maps/Metro by T-Mobile Coverage Maps. We have also provided MetroPCS’s roaming network, MetroPCS Coverage Map by States and MetroPCS Coverage Map by percentage chart.
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
- Crash on SceneVisibilityState when trying to open a project containing another project in the Assets folder
- Reflection probe bounces don't work when Rendering Path is set to 'Deferred'
- Shader error undeclared identifier "UNITY_TRANSFER_LIGHTING" when building project
- Shader effect with specific view disappears when multiple materials in scene are present
- Crash on ShaderLab::IntShader::CreateLocalKeywordRemap when loading custom shaders on standalone build
Resolution Note (fix version 2020.1):
Fixed in Unity 2020.1.0a24
Resolution Note (fix version 2019.3):
Fixed in Unity 2019.3.4f1