Work around the display of warnings about dependency scan analysis#2762
Merged
zorgiepoo merged 1 commit intosparkle-project:2.xfrom Sep 4, 2025
Merged
Conversation
…scovering a dependency of SparkleInstallerLauncher on Sparkle. I thought at first I could add the build setting just to the affectced XPC service target, but since the scan happens at the workspace level it needs to be set on the project.
9e08d74 to
9986ae3
Compare
Member
|
Great, thank you. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Work around the display of warnings about dependency scan analysis discovering a dependency of SparkleInstallerLauncher on Sparkle.
Misc Checklist
Testing
I tested and verified my change by using one or multiple of these methods:
macOS version tested: macOS 26 beta with Xcode 25 beta.