This bug was due to an issue where Interactables were not added to the valid targets list of Direct and Socket Interactors when the Interactable was registered after it had entered the trigger collider of the Interactor, and was fixed in 1.0.0-pre.6 of the package. Interactable objects are automatically registered and unregistered with the XR Interaction Manager during their OnEnable/OnDisable methods, which are also called when the GameObject is activated/deactivated.

The reproduction project submitted with this bug would still need code additions to do what the user expects. They are deactivating the Ball GameObject as they move it away from the Socket, but that means the OnTriggerExit method won't get called on the Socket. As soon as the Ball is activated after firing, it would snap back to the Socket since it would become a valid target again since the event of exiting the trigger was not recorded. The user would need to edit the Cannon's OnSelectExited method to iterate over the colliders and call OnTriggerExit to record the fact that the Ball has exited before moving to storage. The Direct and Socket Interactors use those event methods rather than polling each frame to determine which objects are touching.