Search Issue Tracker
Fixed
Fixed in 2022.3.51f1
Votes
44
Found in
2022.3.40f1
Issue ID
UUM-82547
Regression
Yes
"Missing Prefab Asset" error in a SubScene after Domain Reload
How to reproduce:
1. Open the attached “IN-81743“ project
2. Enter Play Mode
3. Exit Play Mode
4. Change 'MyScript.cs' to trigger a Domain Reload
5. Observe the Unity Console Window
Expected result: No errors are thrown
Actual result: A "Missing Prefab Asset" error is thrown
Reproducible with: 1.1.0-exp.1 (2022.3.40f1, 2022.3.42f1), 1.3.0-pre.4 (2022.3.40f1, 2022.3.42f1)
Not reproducible with: 1.3.0-pre.4 (2022.3.39f1, 6000.0.14f1)
Unable to test: 0.51.1-preview.21 (2021.3.42f1) (Unresolvable package problems due to downgrading)
Reproducible on: Windows 10 (user), Windows 11 pro
Not reproducible on: No other environment tested
Notes:
* Bug regression dependent on the Engine version. Regressed version: 2022.3.40f1
* Once the error occurs, it persists until Unity is restarted
* The Background task “Import EntityScene” remains in a “Not Responding” state
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
- Can not navigate through the Scene view when using a drawing tablet
- Crash on EditorDisplayDialogProc when opening Dialog box containing buttons with unusually long labels
- Crash on AsyncWriteImageToR2dFile when baking lightmaps using custom parameter with 16x Anti Aliasing samples
- Application Cloud Connection Id is incorrect when using Build Profile with Player Setting Overrides.
- [Android] [GameActivity] UI is unresponsive when Application Entry Point is set to GameActivity
deshalb
Aug 22, 2024 16:24
got the same issue here with unity 2022.3.42f1 and entities 1.2.4
DGX-Dino
Aug 22, 2024 12:45
also happens in my project, Entities 1.2.3, Unity 2022.3.40+. Works fine in 2022.3.39
gencontain
Aug 21, 2024 05:25
We're seeing this same issue as well, it's preventing us from upgrading to 2022.3.401f1 and up.
danielkanda
Aug 20, 2024 10:14
I can confirm this issue happens on MacOS as well using 2022.3.41f1 with N4E 1.2.4. Reverting to 2022.3.29 fixed the issue, although I did not test more recent versions.
Hoping this will get resolved quickly as it renders Entities / N4E pretty much unusable.
te_headfirst
Aug 15, 2024 06:45
Pinging this again to make sure it is noticed that this is a production bug in 1.2.3 and not just experimental or pre related.
Also it is our impression that this is not necessarily only related to Entities but could be related to Editor version or even a combination of the two. (seeing that it only happens from 2022.3.40f1 and on.)
te_headfirst
Aug 14, 2024 11:32
We experience the same problem and can say that this is not a preview nor experimental bug. We use Entity Component System 1.2.3 and behaviour is the same. Problem exists in editor version 2022.3.40f1, 2022.3.41f1, and 2022.3.42f1 but not in 2022.3.39f1 (and below).