Search Issue Tracker
By Design
Votes
0
Found in [Package]
1.2.0-preview.11
Issue ID
1206415
Regression
No
[Burst] "Burst error BC1002: Unable to find interface method" error when implementing a job using 2 generic types
Reproduction steps:
1. Open "project_756592.zip" project
2. Build a Standalone Player
Expected Result: Build finishes successfully
Actual Result: Build fails with error "Burst error BC1002: Unable to find interface method `Unity.Entities.IJobForEachWithEntity_ECC`2<SpawnerComponent,SpawnerComponent>.Execute(Unity.Entities.Entity, int, ref T0, ref T1)` from type `BaseSpawnerSystem`2.SpawnerJob`"
Reproduced with: 2020.1.0a18, 2019.3.0f4, 2019.2.17f1
Did not reproduce on: 2018.4.15f1(Scripting errors), 2017.4.36f1(No Packman)
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
- After converting a Built-in project to URP render texture related errors are spammed that can lead to Game view being rendered on top of Scene view
- UI Builder slider value lags and stutters when sliding/modifying certain property values
- "Reset UI Builder Layout" functionality inconsistently changes Canva Size when "Match Game View" is enabled/disabled
- Texture Import Warnings are obscured by other Terrain Layer options in the Inspector
- Burst Inspector middle divider is jittering when resized with the Burst Inspector window docked
Resolution Note:
This behaviour is by-design. It's not currently possible to call job.Schedule(...) if at the call site the job type has generic type arguments that have not been substituted with concrete types. In the call to job.Schedule(...), SpawnerJob has a generic type argument TSpawnerComponentType, which Burst is unable to resolve to a concrete type.