Search Issue Tracker
Fixed
Votes
0
Found in [Package]
1.0.0
Issue ID
1254643
Regression
No
[Input System][Android]Input is not registered with some of the devices
Steps to reproduce:
1. Open user's attached project "I, Mirror.zip"
2. Build it to Android
3. Drag the screen from bottom to top
3. Nothing happens
Expected results: Edgy lines drag with the finger from bottom to top
Actual results: No lines are dragging
Reproducible with: 2020.1.0b14(1.0.0), 2020.2.0a15(1.0.0)
VLNQA00220, Samsung Galaxy Note9 (SM-N960F), Android 8.1.0, CPU: Exynos 9 Series 9810, GPU: Mali-G72
VLNQA00024, Xiaomi Mi 5 (MI 5), Android 7.0, CPU: Snapdragon 820 MSM8996, GPU: Adreno (TM) 530
Not Reproducible with:
VLNQA00123, Google Pixel 2 XL (Pixel 2 XL), Android R, CPU: Snapdragon 835 MSM8998, GPU: Adreno (TM) 540
N/A, Samsung Galaxy S9 (SM-G960F), Android 8.0.0, CPU: Exynos 9 Series 9810, GPU: Mali-G72
VLNQA00313, Huawei Y6 Ⅱ Compact (HUAWEI LYO-L01), Android 5.1, CPU: MediaTek MT6735, GPU: Mali-T720
iPad 7th gen (iOS 13.2.2)
Unable to test with 2019.4 and lower due to dependencies and project braking
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 TextCore::OTL_TableReader::GetOpenTypeLayoutTables when using Japanese Font as TMP Fallback
- TreeView.AddItem performance regression when opening EditorWindow
- Shadows are not visible in Player when using DX12 with Forward+ or Deferred+ rendering in URP
- Rendering Debugger Playmode debug UI scrolling is jittery when using click and drag to scroll
- Frame Debugger Target Selection Search Results window becomes too tiny to even see the default “Editor” selection when there are no search results
Resolution Note:
Fixed in Input System 1.1.1