🐛 Remove Sparkle Sandboxing configuration

[zorgiepoo]

Bug Description

Due to a sandboxing issue new to macOS Sonoma, users may see a one-time warning when checking for updates about "Downloader" differs from previously opened versions. See sparkle-project/Sparkle#2514 for more information.

Loop can simply resolve this issue by removing its sandboxed configuration for Sparkle because Loop itself is not sandboxed. This involves removing the SUEnableDownloaderService and SUEnableInstallerLauncherService keys in its Info.plist, as well as removing the com.apple.security.temporary-exception.mach-lookup.global-name key in its entitlements file. These settings were retrieved from Sparkle's Sandboxing guide but again, this app is not sandboxed.

Steps To Reproduce

NA

Expected Behavior

See bug description

Actual Behavior

See bug description

Screenshots

No response

MacOS Version

macOS 14

Loop Version

1.0.0-beta.14

Additional Context

No response

Final Checks

• My issue title is descriptive
• This is a single bug (multiple bugs should be reported individually)

[mrkai77]

I was wondering why this was happening! Thank you so much for bringing this to my attention! I will definitely fix this!