Search Issue Tracker
Fixed
Fixed in 1.8.0
Votes
0
Found in [Package]
1.5.0
Issue ID
ISXB-779
Regression
No
[InputSystem] Assertion Error (binding resolution) when Destroying and Instantiating OnScreenStick
Reproduction steps:
1. Open the attached Project “BugRepro”
2. Go to Build Settings and enable Development Build
3. Build and Run on an Android device
4. In the Editor open Android Logcat and connect the device
5. Inside the application tap on “Test Bug Execute” button
6. Observe the Android Logcat window
Expected result: No errors produced
Actual result: Multiple errors produced
Reproducible with: 1.4.4 (2020.3.45f1), 1.5.0 (2020.3.45f1, 2021.3.19f1, 2022.2.7f1, 2023.1.0b5, 2023.2.0a4)
Reproducible on: Samsung Galaxy S9 (SM-G960F), CPU: Exynos 9 Series 9810, GPU: Mali-G72, OS: 10.0.0
Google Pixel 3 (Pixel 3), CPU: Snapdragon 845, GPU: Adreno 630, OS: 12.0.0
Built using MacOS 12.6 (Intel)
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 (fix version 1.8.0):
1.8.0 will address the issue as a stable release