Search Issue Tracker
Fixed
Fixed in 1.4.X - Entities, 7000.0.0a1
Votes
0
Found in [Package]
1.3.14 - Entities
7000.0.0a1
Issue ID
ECSB-1690
Regression
No
Exceptions are thrown when using the Schedule() method on Job invocation
How to reproduce:
1. Open the “ScheduleInvocationBug.zip“ project
2. Open the “SampleScene“
3. Enter Play Mode
4. Observe the Console
Expected result: “Works“ info message is logged in the Console
Actual result: “Exception: This method should have been replaced by source gen.“ is logged in the Console
Reproducible in: 1.2.0 1.3.14 (2022.3.62f1, 6000.0.49f1, 6000.1.4f1, 6000.2.0b1)
Could not test in: 1.0.8 (2022.3.62f1, 6000.0.49f1) (Burst related package errors)
Reproduced on: Windows 11 Pro (24H2)
Not reproduced on: No other environment tested
Workaround: In code, create the Job object before using the Schedule() method
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
- Blank, Light-Themed "Create Node" window becomes visible on the next project open
- UI Elements/Layout inconsistencies in the Particle System component
- The Game view and Scene view fail to render when launching the Editor with a maximized Render Graph Viewer window
- "List is empty" is poorly visible in the "Create Node" window
- [Android] GameObject with a custom shader becomes invisible when deployed with the Vulkan Graphics API
Resolution Note (fix version 7000.0.0a1):
Scheduling a job in Runtime from a method invocation will no longer throw "Exception: This method should have been replaced by source gen."
Resolution Note (fix version 1.4.X - Entities):
Scheduling a job in Runtime from a method invocation will no longer throw "Exception: This method should have been replaced by source gen."