UUM-47104
Fixed in 2022.3.10f1Mentioned in 6 release notes.
First fixed in 2022.3.10f1 (Sep 19, 2023); relisted in 5 later releases.
| Version | Section | Risk | Impact | Note |
|---|---|---|---|---|
| 6000.0.0b16 | Fixes Android | Fix | Fixed Input.multiTouchEnabled setter. Previously, for some platform, if the setter was called before any touch event, the values would be disregarded. | |
| 6000.0.0b15 | Fixes Android | Fix | Fixed Input.multiTouchEnabled setter. Previously, for some platform, if the setter was called before any touch event, the values would be disregarded. | |
| 6000.0.0b13 | Fixes Android | Fix | Fixed Input.multiTouchEnabled setter. Previously, for some platform, if the setter was called before any touch event, the values would be disregarded. | |
| 6000.0.0b12 | Fixes Android | Fix | Fixed Input.multiTouchEnabled setter. Previously, for some platform, if the setter was called before any touch event, the values would be disregarded. | |
| 6000.0.0b11 | Fixes Android | Fix | Fixed Input.multiTouchEnabled setter. Previously, for some platform, if the setter was called before any touch event, the values would be disregarded. | |
| 2022.3.10f1 | Fixes Android | Fix | Fixed Input.multiTouchEnabled setter when it's called before any touch event, previously such values would be disregarded since internally there was no touch device available for multiTouch to set to. |