Search Issue Tracker
Won't Fix
Votes
1
Found in
2021.3.28f1
2022.3.5f1
Issue ID
UUM-44011
Regression
No
“UnityException: Load is not allowed to be called during serialization” error is thrown when using Resources.Load method in a serialized class
Reproduction steps:
1. Open the attached “ASDQWE” project
2. Open the “Assets/Scenes/Menu.unity” Scene
3. Enter the Play Mode
4. Press enter multiple times to progress the game
5. When the “BaseTemplate.unity” Scene has been loaded, exit the Play Mode
6. Enter the Play Mode
7. Observe the Console Window
Expected result: No error is thrown
Actual result: “UnityException: Load is not allowed to be called during serialization” error is thrown
Reproducible with: 2021.3.28f1, 2022.3.5f1
Could not test with: 2023.1.5f1 (two “error CS0246: The type or namespace name 'ShadowCaster2D' could not be found” errors), 2023.2.0b1 (“error CS0266: Cannot implicitly convert type 'UnityEngine.Vector4*' to 'UnityEngine.Vector2*’”)
Reproducible on: Intel macOS 13.4
Note: The error does not pause the Play Mode
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
- Prefab Override popup displays on wrong monitor when Inspector width is resized to minimum
- Scroll View is not moving by inertia after scrolling by click and dragging when Editor window is minimized and Canvas "Render Mode" is set to "World Space"
- "type mismatch error" occurs when the currentDirectionWS output of a Sample Water Surface node is connected to a float3 input
- URP Material Upgrade utility does not enable Alpha Clipping when material had Rendering Mode set to Cutout
- Particle System emission ignores the Sprite Atlas when using a Material that has the "Include in Build" setting unchecked
Resolution Note:
Thank you for reporting a bug to Unity.
We have reviewed the issue carefully, and in this case, the team is unable to prioritize fixing this bug. There are a number of reasons we make this decision, including the impact and severity of the issue across our user and customer base, and the possibility that future plans may solve the problem in a different way, or that a workaround for the bug may be available.
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.