![]() In the unusual case that you cannot add entitlements (e.g. If you are building your application in Xcode, $(PRODUCT_BUNDLE_IDENTIFIER) will be automatically substituted with your application’s bundle identifier. To allow Sparkle to communicate to its running installer tools, you will need to add the following entitlement to your sandboxed application:Ĭom.-lookup.global-name $(PRODUCT_BUNDLE_IDENTIFIER)-spks $(PRODUCT_BUNDLE_IDENTIFIER)-spki To enable the service, you must set SUEnableInstallerLauncherService boolean to YES in your application’s ist. This service lets Sparkle install updates outside of your application’s sandbox. Sparkle by default bundles this XPC Service in its framework bundle. The Installer XPC Service is required for Sandboxed applications. Please read the below sections on full integration details. Downloader.xpc ( prior to Sparkle 2.2 optional).Sparkle by default bundles two XPC Services inside the framework for sandboxing your application: In order for Sparkle to function in a sandboxed environment, the application must call out to XPC Services and ensure the application’s entitlement requirements are met. ![]() ![]() You will need to stop bundling the XPC Services directly inside your application and add ist keys to enable the services. If you are migrating from an older beta version of Sparkle 2, the XPC Services have been moved into Sparkle’s framework bundle. If you do not sandbox your application, you may skip this page unless you are interested in Removing the XPC Services. Using Sparkle in a sandboxed application is only supported in Sparkle 2.
0 Comments
Leave a Reply. |