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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Resolution Note:
Fixed in Input System 1.1.1