Search Issue Tracker
Duplicate
Votes
0
Found in
2020.1
2020.1.0b8
Issue ID
1246565
Regression
No
UI is not responsive after opening Android Native popup Dialog
How to reproduce:
1. Build and run the attached "TouchBugDemo.zip" project to an Android device
2. Click "Open" button (red rectangle should appear at the top left of the screen)
3. Try to click any of the buttons in the scene
Expected Behavior: Buttons are responsive (shows click animation) and button "log" prints logs like "hello" to the console
Actual Behavior: UI buttons are not responsive
Reproducible with: 2020.1.0b13
Coult not test with: 2020.2, 2019.4, 2018.4 due to Gradle dependency errors during the build
Devices reproduced:
VLNQA00015, Samsung Galaxy Note8 (SM-N950W), Android 8.0.0, CPU: Snapdragon 835 MSM8998, GPU: Adreno (TM) 540
VLNQA00285, Samsung Galaxy J4 Core (SM-J410F), Android 8.1.0, CPU: Snapdragon 425 MSM8917, GPU: Adreno (TM) 308
VLNQA00286, Meizu - (PRO 5), Android 7.0, CPU: Exynos 7 Octa 7420, GPU: Mali-T760
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
- 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
- The layout system is failing to correctly calculate or apply the height of the Japanese fallback font when the primary English font's metrics are used
This is a duplicate of issue #1255346