Search Issue Tracker
Fixed
Fixed in 3.1.0
Votes
0
Found in [Package]
3.0.7
3.1.0-pre.1
Issue ID
XRIT-210
Regression
Yes
[ARDemoScene][iOS] Next tap event lost after object deletion
Steps to reproduce:
1. Unzip and open attached project.
2. Use Unity 2022.3.52f1 or 6000.0.25f1 to open the ARDemoScene scene.
3. In Build Settings, add current scene and switch platform to iOS.
4. Build and Run.
5. Do whatever you normally do in Xcode to deploy to your iOS device.
6. Scan your real world environment until you find a plane.
7. Tap the plane several times to spawn a few objects.
8. Tap an object to select it.
9. Tap the trash can icon to delete the selected object.
10. Tap another object to select it.
Actual results:
Your tap event does not select the object. Instead, it might fall through to the plane and spawn another object.
If you tap the object again then it will be selected. But if you delete this object, then then next selection tap will be ignored...
Expected results:
Your tap should select the tapped object, making it highlight.
Reproducible with versions:
Unity 2022.3.52f1 and 6000.0.25f1.
Not reproducible with versions:
Unity 2021.3.45f1.
Can’t test with versions:
Tested on (OS):
MacBook Pro - M1 Pro; MacOS 14.6.1
iPhone 13; iOS 17.3.1
Notes:
- This is a regression because it did not repro in 2021.3. During earlier testing it might have been masked by other selection bugs.
- There is a separate tap bug on Android: XRIT-208.
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 (fix version 3.1.0):
Changed `XRUIInputModule` to now initialize to the Input System when active input handling in Project Settings is set to Input System Package (New) or Both. The issue here was that the Touch processing for legacy Input Manager was causing issues with the Touch for Input System and events were getting missed.