You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Due to a sandboxing issue new to macOS Sonoma and due to this app and other apps using Sparkle's Downloader XPC Service, users may see a one-time system warning dialog when checking for updates about "Downloader" differs from previously opened versions.
It looks like KeepingYouAwake wants to use the Sparkle's Downloader XPC Service from following Sparkle's sandboxing guide because the app is not entitled with an outgoing network connection (com.apple.security.network.client) entitlement. So there are a couple ways to fix this issue:
KeepingYouAwake can update to Sparkle 2.6.0 or later (which disables sandboxing for the Downloader XPC Service by default to avoid conflicts) (easiest way)
KeepingYouAwake can re-compile their current version of Sparkle with a custom XPC_SERVICE_BUNDLE_ID_PREFIX
KeepingYouAwake can enable the outgoing network connection (com.apple.security.network.client) entitlement on its app instead of enabling the Downloader XPC Service as there are other drawbacks with using the downloader service (e.g. Sparkle can't use WebKit 2).
Due to a sandboxing issue new to macOS Sonoma and due to this app and other apps using Sparkle's Downloader XPC Service, users may see a one-time system warning dialog when checking for updates about "Downloader" differs from previously opened versions.
It looks like KeepingYouAwake wants to use the Sparkle's Downloader XPC Service from following Sparkle's sandboxing guide because the app is not entitled with an outgoing network connection (
com.apple.security.network.client
) entitlement. So there are a couple ways to fix this issue:XPC_SERVICE_BUNDLE_ID_PREFIX
See sparkle-project/Sparkle#2514 and the updated sandboxing guide for more information on the issue.
[edit]: Updated to include 3rd option of not using downloader service.
The text was updated successfully, but these errors were encountered: