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
- "IndexOutOfRangeException" and "NullReferenceException" are thrown and Element disappears from UI Builder when undoing rename of element in "Open Instance in Context" menu
- Select Scriptable Object window freezes and becomes unresponsive when currently opened UXML Template is selected for binding's Data Source
- [Linux] “ReleaseButton expects buttonId >= 0” error is thrown when importing Assets via drag and drop
- Asset gets unselected and added Subgraphs list item is not undone when performing Undo in Heatmap with Default Values asset Inspector
- Black square “shadow” artifacts visible when using Screen Space Reflections without maximum smoothing
Add comment