fix(@capacitor/haptics): prevent thread overload by reusing CHHapticEngine #2340
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fix: Prevent iOS app freeze by reusing
CHHapticEngine
instanceThis PR addresses an issue where calling
Haptics.vibrate()
rapidly (e.g., from a fast-scrolling picker in my case) causes the app to hang or crash on iOS. The problem stems from creating a newCHHapticEngine
instance on each call, which leads to excessive thread creation and eventual system overload.Solution
CHHapticEngine
instance across multiple vibration calls.This fix improves performance and stability, especially in high-frequency vibration scenarios.
Related Issue #1960