Search Issue Tracker
Fixed
Fixed in 2020.3.46f1, 2021.3.19f1, 2022.2.7f1, 2023.1.0b1
Won't Fix in 2022.1.X
Votes
1
Found in
2020.3.36f1
2021.3.5f1
2022.1.7f1
2022.2.0a18
Issue ID
UUM-6667
Regression
No
Touch input is reset in Device Simulator when Unity Remote is killed
How to reproduce:
1. Open the attached project "InputLostTest.zip" and load Scene "SampleScene"
2. Open Unity Remote on a mobile device
3. In Project Settings -> Editor ensure the correct mobile device is selected
4. Enter Play Mode
5. In the Device Simulator (Window -> General -> Device Simulator) use the mouse to simulate a continuous touch
6. Without releasing your mouse, kill Unity Remote on the mobile device
Expected result: touch input does not get reset in Device Simulator
Actual result: touch input gets reset in Device Simulator
Reproducible with: 3.0.3-preview (2020.3.36f1), 2021.3.5f1, 2022.1.7f1, 2022.2.0a18, 2022.3.0a1
Notes:
- Ordinarily, any kind of touch on the Remote app resets the touch input from Device Simulator, however just putting the Remote app in the background does not reset it
- Reproducible both on iOS and Android
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
- ACES Tonemapping causes banding artifacts and negative values in ColorGradingLUT when HDR is enabled and "High Dynamic Range" Grading mode is selected while Android Platform is used
- Android Player freezes when an Audio Source is playing and an incoming call is picked up and then hung up and the Audio Source is started again
- Green success icon is poorly visible in the light Unity theme
- Incorrect input into the Input Field when using Microsoft IME Japanese
- Multiplayer role "ClientAndServer" is displayed without the spaces in the "Play Mode Scenarios" window
Resolution Note (2022.1.X):
Reached end of life