Swift Package Manager: Fix NS_BLOCK_ASSERTIONS for release builds #869
Open
jjkaufman wants to merge 1 commit intoopenid:masterfrom
Open
Swift Package Manager: Fix NS_BLOCK_ASSERTIONS for release builds #869jjkaufman wants to merge 1 commit intoopenid:masterfrom
jjkaufman wants to merge 1 commit intoopenid:masterfrom
Conversation
ankushkushwaha
approved these changes
Nov 14, 2024
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.
There is an issue in Swift Package Manager where any NSAssert inside of packages will throw fatal exceptions on release builds.
I don't believe this is intentional behavior of AppAuth. Including a new cSettings in the Package.swift file resolves the issue.
Here is a thread on the Swift forums discussing the issue
https://forums.swift.org/t/assertions-in-swift-packages/42692