Search Issue Tracker
Won't Fix
Votes
1
Found in
2019.4.39f1
2020.3.35f1
2021.3.3f1
2022.1.2f1
2022.2.0a15
2023.2.0a1
Issue ID
UUM-1724
Regression
No
MouseButton(0) loses click state when using Device Simulator and enabling "Any iOS Device" in Unity Remote
How to reproduce:
1. Open project "UnityRemote.zip"
2. Open Menu > Edit > Project Settings > Editor and select "Any iOS Device" in the Device list
3. Enter Play Mode and open the Console window
4. Open Menu > General > Device Simulator, hold mouse left button pressed on the Simulator screen
5. Observe the Console window
Expected result: "True" is logged
Actual result: "False" is logged after a few seconds
Reproducible with: 1.0.0-preview (2019.4.39f1), 3.0.3-preview (2020.3.35f1), Built-in (2021.3.3f1, 2022.1.2f1, 2022.2.0a15)
Reproducible on: macOS 11.6 (Intel)
Note: Not reproducible when choosing "Any Android Device" or "None" in the Device list
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
- var VisionOSEDRHeadromm has a comma instead of a dot when building with Metal Rendering App Mode and local OS localization is set to German
- IAP Catalog remove product “x” and add product “+” buttons are not consistent with other remove and add buttons in the Editor
- Performance issues in Play Mode when quickly hovering the mouse cursor over Hierarchy GameObjects
- Frame Debugger displays incorrect output when FidelityFX Super Resolution or Spatial-Temporal Upscaler is used with Temporal Anti-aliasing or Subpixel Morphological Anti-aliasing
- The layout system is failing to correctly calculate or apply the height of the Japanese fallback font when the primary English font's metrics are used
Resolution Note:
Thank you for reporting a bug to Unity.
We have reviewed the issue carefully, and in this case the team is unable to prioritize fixing this bug. There are a number of reasons we make this decision, including the impact and severity of the issue across our user and customer base, and the possibility that future plans may solve the problem in a different way, or that a workaround for the bug may be available.
Today we will be closing this case. Thank you again for taking the time to report this issue, and please let us know if there is anything else that changes the impact or severity of this issue.