*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:*
* This bug might have been masked in earlier versions by [XRIT-145|https://jira.unity3d.com/browse/XRIT-145] and/or [XRMART-2|https://jira.unity3d.com/browse/XRMART-2]. 
* There is a separate tap bug on iOS: [XRIT-210|https://jira.unity3d.com/browse/XRIT-210].