Check for updates once daily

[akramj13]

Summary

• enforce a 24-hour Sparkle update-check interval for existing and new installations
• remove the unconditional background update check on every app launch
• preserve manual update checks from the menu bar and Settings

Fixes #768

Root cause

Sparkle persists its update interval in user defaults, which take precedence over the value in CotabbyInfo.plist. Existing installations could therefore retain a shorter interval. Cotabby also called checkForUpdatesInBackground() on every launch, bypassing Sparkle's normal last-check scheduling.

User impact

Automatic update checks now occur at most once per day. Sparkle continues to use its persisted last-check date, while users can still request an immediate check manually.

Validation

• git diff --check
• plutil -lint CotabbyInfo.plist
• unsigned production build: xcodebuild -project Cotabby.xcodeproj -scheme Cotabby -destination 'platform=macOS' build -derivedDataPath build/DerivedData CODE_SIGNING_ALLOWED=NO -quiet
• verified the built app contains SUScheduledCheckInterval = 86400

Greptile Summary

This PR changes Sparkle update checks to follow a daily cadence. The main changes are:

• Applies a 24-hour automatic update-check interval in code.
• Starts Sparkle with that interval before scheduling begins.
• Replaces the launch-time unconditional background check with a last-check-date catch-up check.
• Keeps manual update checks available through existing UI paths.

Confidence Score: 4/5

This is close, but one launch-check behavior should be fixed before merging.

• The catch-up path can still run a background update check when automatic checks are disabled.
• The interval and last-check-date logic otherwise matches the intended daily cadence.

Cotabby/Services/Utilities/AppUpdateManager.swift

Important Files Changed

Filename	Overview
Cotabby/Services/Utilities/AppUpdateManager.swift	Applies the daily Sparkle interval and adds a launch catch-up check based on the persisted last-check date.

_{Reviews (3): Last reviewed commit: "fix: catch up overdue update checks at l..." | Re-trigger Greptile}

Greptile also left 1 inline comment on this PR.

[akramj13]

@greptileai

[akramj13]

@greptileai

[greptile-apps]

Respect Disabled Checks

When automatic update checks are disabled, this catch-up path can still call checkForUpdatesInBackground() after the stored last-check date is missing or older than 24 hours. That makes launch contact the update feed even though the user disabled automatic checks. Gate the catch-up call on automaticallyChecksForUpdates so manual checks still work while automatic launch checks stay off.

Suggested change

	if shouldCatchUp {
	updater.checkForUpdatesInBackground()
	}
	if updater.automaticallyChecksForUpdates && shouldCatchUp {
	updater.checkForUpdatesInBackground()
	}