Search Issue Tracker
Fixed
Fixed in 3.0.8, 3.1.0
Votes
0
Found in [Package]
3.0.7
3.1.0-pre.1
Issue ID
XRIT-208
Regression
No
[ARDemoScene][Android] Slow tap fails to spawn or select objects
Steps to reproduce:
1. Unzip ARDemoScene_ARCore.zip (see attached) and open the project with Unity 6000.0.25f1.
2. Build-and-Run on an Android phone; I used S21.
3. Scan a plane and tap on it to spawn objects. Tap each of your spawned objects to select each of them in turn.
Actual results:
If your tap is quick and gingerly, then it is recognized as a tap; an object is created or selected as intended.
If your tap is slower then it is ignored (no object is selected or created) unless you actually do a tap-and-drag (i.e. touch the screen then move your finger across the screen at least a small distance prior to releasing).
Expected results:
By default AR apps made with XR Interaction Toolkit should honor tap durations that work in the basic UI of iOS and Android phones. I can launch apps on my phones using taps that are too slow for ARDemoScene.
Reproducible with versions: XRI 3.0.7 and some earlier versions.
Not reproducible with versions:
Can’t test with versions:
Tested on (OS):
MacBook Pro - M1 Pro
MacOS 14.6.1
Notes:
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- "No HDR monitor detected." warning is shown in the Rendering Debugger even when the Editor is on HDR-enabled monitor
- Shader Graph Enum Keyword Default Value changes after reordering Entries
- Light Explorer throws “ArgumentException” error when disabling all columns from the Multi-column panel context menu
- "Freeze Camera For Culling" options are inconsistent between the Game view overlay and Rendering Debugger window
- Crash on GetOriginalSourceOrVariantRoot when creating a scene from a specific template
Add comment