Search Issue Tracker
Won't Fix
Votes
1
Found in
2018.1.0b13
Issue ID
1022097
Regression
No
Scriptable Object with missing Script behaves differently in PlayMode and in PlayMode Tests
Reproduction steps:
1. Download user's project and open in Unity
2. Enter Play mode - everything works fine
3. Open Window -> Debug -> Test Runner and select PlayMode
5. Select "Run All"
6. Run tests again
Expected: behavior is the same in Play mode and in PlayMode tests
Actual: PlayMode tests fail
Reproduced on: 2017.1.3p4; 2017.2.2p4; 2017.3.2f1; 2017.4.1f1; 2018.1.0f1; 2018.2.0b1
Note: "Resources/String With Int" in inspector has a warning - "The associated script cannot be loaded. Please fix any compile errors and assign a valid script."
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
- [Android] Stage information is not logged when Log Shader Compilation is enabled
- [Vulkan] The memory allocation increases rapidly when there are multiple (three or more) Real-Time Reflection Probes in the Scene
- [macOS] Library folder of the opened project can be deleted which leads to the crash
- “Default Scene” dropdown field contains a spelling mistake “Default Builtin”
- Editor crashes on PPtr<Mesh> after adding Text Mesh and Cloth Components to the same GameObject
Resolution Note:
Closed as wont fix, as the workaround "Always put Scriptable Objects in Files with the same name. This prevents missing Scripts." is the recommended approach in general. The test framework will have unpredictable behavior when working with missing scripts.