You can use SpeechTranscriber.Preset to configure settings tailored to specific use cases. If you prioritize real-time recognition, specifying .progressiveTranscription should make it somewhat faster and improve responsiveness. https://developer.apple.com/documentation/speech/speechtranscriber/preset let preset = SpeechTranscriber.Preset.progressiveTranscription let transcriber = SpeechTranscriber( locale: Locale.current, transcriptionOptions: preset.transcriptionOptions, reportingOptions: preset.reportingOptions, attributeOptions: preset.attributeOptions )

Thanks for the clarification. As a workaround, I’ve found that controlling visibility using OpacityComponent (instead of disabling the Entity or removing it from the scene) avoids this issue. When the Entity remains in the hierarchy and only its opacity is changed, tap interactions continue to work correctly. However, OpacityComponent is fundamentally intended for visual transparency, not for lifecycle or removal control. Using it as a substitute for disabling or removing an Entity could lead to unintended behavior in cases where actual removal is required by the app’s design. I wanted to share this finding for reference, but it would still be helpful to have a supported way to temporarily disable or remove an Entity with ViewAttachmentComponent without breaking gesture handling.