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
- Crash on JobQueue::HasJobGroupIDCompleted when closing the Editor while in Play mode on a specific project
- In "Preferences" section the “SpriteShape” menu item, the details page title “SpriteShape”, and “ControlPoint” entries are displayed as code strings rather than formatted UI strings
- Errors thrown constantly when Virtual Offset Debug is enabled and lighting was baked on AMD machine
- Persistent Memory Leak when reloading domain and using Distance-based Ghost Importance
- HDRP project doesn't render in standalone player when using High stripping
Add comment