Optimize watch managers to skip processing when no watch is connected #674
+41
−1
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.
Watch Manager Optimizations
This PR improves app performance by preventing unnecessary processing when no watch is connected. It addresses two key issues:
Apple Watch & Garmin Watch Optimizations
Problem
The app was previously creating tasks and performing expensive calculations for watch data even when no watch was connected or the watch app wasn't installed.
Solution
Added early-return guards in both watch managers:
BaseWatchManager.setupWatchState
now checks if a watch is paired, the session is reachable and the app is installedBaseGarminManager.setupGarminWatchState
now checks if any Garmin devices are connectedOptimized CoreData publishers to prevent task creation:
Performance Impact
These changes can potentially reduce CPU and memory usage when no watch is connected, as the app no longer:
TODO