Search Issue Tracker
Fixed
Fixed in 3.0.8
Votes
0
Found in [Package]
3.0.7
3.1.0-pre.1
Issue ID
XRIT-209
Regression
Yes
"ArgumentException: An item with the same key has already been added. Key: Cube" is thrown when poking an object with multiple colliders
How to reproduce:
1. Open the attached project "IN-88459.zip"
2. Open Assets/Scenes/IN-88459.unity
3. Connect Quest 2 with Meta Quest Link
4. Enter Play Mode
5. Touch the Cube with the controller
Expected results: No errors are thrown in the Console window
Actual results: "ArgumentException: An item with the same key has already been added. Key: Cube" is thrown
Reproducible with: 3.0.0-pre.2 (2021.3.46f1, 2022.3.53f1), 3.0.7 (2021.3.46f1, 2022.3.53f1, 6000.0.28f1, 6000.1.0a5)
Not reproducible with: 3.0.0-pre.1 (2021.3.46f1, 2022.3.53f1)
Reproducible on these devices:
Oculus (Quest 2), Android 12.1, CPU: Snapdragon XR2, GPU: Adreno (TM) 650
Reproducible on: Windows 10 22H2
Not reproducible on: No other environment tested
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
- “MissingReferenceException”, “NullReferenceException” and GUI errors are spammed in the Console when selecting “Boris” GameObject in the Prefab field of the “Plunkah” GameObject in the “_IK” Sample scene
- "Upload Symbols Failed" is thrown when Archive validation is being done in Xcode
- Active quality level set on a new Universal 2D project is not the default quality level when creating a new project
- Inspector Open button does nothing when navigating to a different folder with a locked asset
- Pre-generated XML serializers fail to deserialize types that use polymorphism when the Player is built with the IL2CPP scripting backend
Resolution Note (fix version 3.0.8):
This fixes an issue where the Poke Interactor was trying to register a valid target twice for 2 or more successful poke overlaps for a given interactable. This fix simply checks if the valid targets list already contains a reference to the same interactable and skips it.
Resolution Note:
This fixes an issue where the Poke Interactor was trying to register a valid target twice for 2 or more successful poke overlaps for a given interactable. This fix simply checks if the valid targets list already contains a reference to the same interactable and skips it.