Search Issue Tracker
Fixed
Fixed in 2022.3.10f1
Votes
0
Found in
2022.3.9f1
Issue ID
UUM-49726
Regression
Yes
UI elements become unresponsive with an error "Composite count in old and new state must be the same" after loading a different Scene in the Play Mode with the Android Platform selected
How to reproduce:
1. Open the "IN_54306" project
2. Open the “Map” Scene
3. Enter the Play Mode
4. In the Game View press the red dot on the map
5. Once the “FillingCrumbly” Scene opens try clicking on the UI elements in the top right corner of the Game View
6. Repeat steps 3-5 couple times
Expected result: UI elements are responsive and no error is thrown in the Console
Actual result: UI elements become unresponsive and the error "Composite count in old and new state must be the same" is thrown in the Console
Reproducible with: 2022.3.2f1, 2022.3.9f1
Not reproducible with: 2022.3.1f1, 2023.1.14f1, 2023.2.0b10, 2023.3.0a4
Couldn't test with: 2021.3.30f1 (due to an error in the Console before entering the Play Mode)
Fixed in: 2022.3.10f1
Reproducible on: Windows 10 Pro
Not reproducible on: No other environments tested
Note: not reproducible in the Player
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- [UI Builder] Viewport's gizmos for Margin and Padding disappear when dragging to modify the value and the cursor leaves the Spacing section
- "Multiplayer Center" window does not reflect changes made in "Other Packages" section
- Crash on D3DKMTOpenResource when capturing with RenderDoc while GPU Skinning is set to GPU(Batched)
- Editing and saving Curve changes in UI Builder window throws multiple errors in the Console
- [UI Builder] Value is not selected when left clicking on Spacing/Border Widget values
Add comment