Search Issue Tracker
By Design
Votes
0
Found in [Package]
0.2.3, 0.2.4
Issue ID
1196574
Regression
Yes
[Entities][Physics] "ArgumentException: There are no more items left to be read" is thrown when GetComponentData is called
How to reproduce:
1. Open attached project "CollisionSample.zip" and scene "Sample Scene"
2. Enter Play mode
3. Observe Console window
Expected result: "Collides!" is printed
Actual result: "ArgumentException: There are no more items left to be read." error is thrown
Reproducible with: 2019.2.12f1, 2019.3.0b10, 2020.1.0a12 (0.2.3, 0.2.4 previews)
Not reproducible with: 2019.2.12f1 (0.2.0, 0.2.2 previews)
Could not test with: 2017.4, 2018.4 due to missing ICollisionEventsJob and other package manager errors
Different Package Versions:
"ICollisionEventsJob could not be found" error is thrown (Physics package previews 0.0.1, 0.0.2)
"InvalidOperationException: The previously scheduled job BlockStream:ConstructJob writes to the NativeArray ConstructJob.BlockStream" error is thrown (preview 0.1.0)
"Collides!" is printed 51 times (previews 0.2.0, 0.2.2)
"ArgumentException: There are no more items left to be read." error is thrown (previews 0.2.3, 0.2.4)
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
- Edge detection fails, _BlitTexture_TexelSize is 0
- Rotating GameObjects is not possible when transform.up is assigned through script
- [Android] Shadowmap Shadows have graphical errors on Android when the default Screen Recorder setting is turned on
- Editor crashes on physx::PxcDiscreteNarrowPhasePCM or freezes when instantiating many GameObjects
- [RenderingDebugger] Wireframe mode is not fully rendered in the Scene View
Resolution Note:
Hard to discern the user's intent from the attached example, but it seems to be user error. I've attached an example demonstrating more correct usage based on what I think they're trying to do.