Search Issue Tracker
By Design
Votes
0
Found in
2022.2.2f1
2023.1.0a20
2023.2.0a1
Issue ID
UUM-22071
Regression
No
VisualElement.style.visibility doesn't get set to Visibility.Hidden or StyleKeyword.Null for IL2CPP Android builds
How to reproduce:
1. Open the user’s attached “UIToolkit.zip“ project
2. Build and Run the “SampleScene“ Scene for Android
3. Touch the screen
4. Open the Android Logcat window and profile a device
5. Observe printed messages
Expected result: “CURRENT VISIBILITY is: Null”, “style.visibility == StyleKeyword.Null”, “style.visibility != Visibility.Hidden“ messages appear
Actual result: “CURRENT VISIBILITY is: Null”, “style.visibility != StyleKeyword.Null”, “style.visibility != Visibility.Hidden“ messages apeear
Reproducible with: 2022.2.2f1, 2023.1.0a20
Not reproducible with: 2021.3.16f1, 2023.1.0a21, 2023.1.0a25
Couldn’t test with: 2020.3.44f1 (Package errors after downgrade)
reproducible with these devices:
Huawei - (ELS-NX9), Android 10, CPU: HiSilicon Kirin 990 5G, GPU: Mali-G76
Samsung Galaxy Z Flip3 5G (SM-F711B), Android 12, CPU: Snapdragon 888, GPU: Adreno (TM) 660
Samsung Galaxy S22 (SM-S901B), Android 12, CPU: Exynos 2200, GPU: Ltd.
Samsung Galaxy S10+ (SM-G975F), Android 10, CPU: NOT FOUND, GPU: Mali-G76
Not reproducible with these devices:
VLNQA00494 - iPhone 14 Pro Max, 16.0.3 iOS
VLNQA00358 - iPhone 12, 14.1 iOS
VLNQA00392 - iPad (9th generation), 15.0 iOS
VLNQA00310 - iPad Pro 12.9", 13.4.1 iOS
Notes:
- Not reproducible in the Editors Play mode
- Not reproducible with the Mono Scripting Backend
- The issue is also reproducible when style.visibility is set to Hidden in Hierarchy > Visibility Null Bug (Script) > Set Bg Visibility Hidden
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
- Crash on ConvertBufferToEXRBuffer when Lighting Generation is cancelled
- [URP] TrailEffect in URP package samples does not draw Trail Effect
- "NullReferenceException" error is thrown when calling UIDocument.runtimePanel in OnEnable with ExecuteInEditMode
- Graphics.Blit() performs the operation only to the last display when a multi-display environment is used
- [Windows] Multiple Separation Lines are present in the Light Create Menu
Resolution Note:
Cannot reproduce. Using 2022.2.8 (latest staging) the issue does not reproduce.
Looks like this is duplicate of something that is in flight of being backported.