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
- Crash on when D3D12RenderPass::SetupDeviceResources when opening FBX animation preview
- Serialization errors are thrown when "com.unity.render-pipelines.core" is added as a custom package and Graphics window is opened
- Character Joints unexpectedly rotate when a ragdoll is created using the Ragdoll Wizard
- Crash on GfxDeviceD3D11Base::DrawBuffersBatchMode when rendering the Scene view
- The shared EditorBuildSettings.asset file of symlinked projects is not updated when changing the order of the Scenes in Build Settings in one of the projects
Resolution Note (fix version 1.8.0):
1.8.0 will address the issue as a stable release