Primary and secondary touch positions the same?

Using the simulator and the PolySpatialInputActions in the sample project, is anyone finding that the primary and secondary touch .interactionPosition’s are sometimes in exactly the same position?

Is this a known bug?

Hello, we haven’t heard of this issue specifically, but feel free to raise a bug with the relevant project details so we can look into it. Thanks!