Search Issue Tracker
Won't Fix
Won't Fix in 1.4.X
Votes
0
Found in [Package]
1.4.2
1.4.3
Issue ID
ISXB-348
Regression
No
Opening the project throws a "System.ArgumentException: An item with the same key has already been added. Key: UnityEngine.InputSystem.InputActionMap[]" error in the Console
How to reproduce:
1. Open the user’s attached project
2. Observe the Console
Expected result: No errors are thrown
Actual result: “(0,0): error System.ArgumentException: An item with the same key has already been added. Key: UnityEngine.InputSystem.InputActionMap[]” error is thrown
Reproducible with: 1.4.2 (2021.3.13f1), 1.4.3 (2022.1.21f1, 2022.2.0b12, 2023.1.0a17)
Couldn’t test with: 1.4.3 (2020.3.41f1) (Console errors)
Reproducible on: Windows 10
2022.2 and 2023.1 produce a different error: “Processing assembly Library/Bee/artifacts/1900b0aE.dag/Assembly-CSharp.dll, with 136 defines and 304 references
processors […]
FishNet.CodeGenerating.ILCore.FishNetILPP: ILPostProcessor has thrown an exception: System.ArgumentException: An item with the same key has already been added. Key: UnityEngine.InputSystem.InputActionMap[]
[…]”
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
- Unity CIL Linker fails on Player build when persistent listeners have "<" and ">" in their XML attribute names
- ”Lighting data asset ‘LightingData’ is incompatible with the current Unity version…” warnings are thrown when saving Indoors (URP) and Outdoors (URP) Scenes as Scene Templates
- [iOS] The screen blinks when transitioning from custom to Unity splash screen
- [macOS] ”Ignoring depth surface load action as it is memoryless” warnings are thrown when taking Game View Snapshot
- UI Builder Inspector scrolls back up when changes on an expanded but not fully displayed Inspector tab are saved
Resolution Note:
There are no fixes planned for this Bug
Resolution Note (1.4.X):
Issue from a 3rd party library (Fishnet) in the user project.