Search Issue Tracker
Fixed in 1.3.0
Fixed in 1.2.13
Votes
0
Found in [Package]
1.0.0, 1.3.0-preview.6
Issue ID
1210877
Regression
No
[Timeline] ArgumentException in SignalReceiver when all Signals are set to None
In SignalReceiver component with 2 or more Reactions, "ArgumentException: SignalAsset already used." error is thrown when the last Signal slot is set to 'None'.
How to reproduce:
1. Open "SampleScene" from project "f4-bugs.zip"
2. In Hierarchy select "SignalReceiver"
3. In Inspector set both Signal selections to 'None'
4. Inspect Console
Expected result: No errors in Console
Actual result: ArgumentException error in Console
Reproducible with: 2019.2.18f1(1.1.0), 2019.3.0f5(1.2.10), 2020.1.0a19(1.3.0-preview.6)
Could not test with: 2017.4 and 2018.4 - Signals not supported
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- var VisionOSEDRHeadromm has a comma instead of a dot when building with Metal Rendering App Mode and local OS localization is set to German
- IAP Catalog remove product “x” and add product “+” buttons are not consistent with other remove and add buttons in the Editor
- Performance issues in Play Mode when quickly hovering the mouse cursor over Hierarchy GameObjects
- Frame Debugger displays incorrect output when FidelityFX Super Resolution or Spatial-Temporal Upscaler is used with Temporal Anti-aliasing or Subpixel Morphological Anti-aliasing
- Crash with “Fatal Error! The file ‘MemoryStream’ is corrupted!” when adding a large number in Font Character Rects Size field
Add comment