fix: Designate SwiftUI a weak_framework in podspec #892
Conversation
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.
Issue #, if available: #878
Description of changes:
Explicitly notes SwiftUI as a
weak_frameworkto work around what I'm assuming is an Xcode or CocoaPods bug where SwiftUI isn't properly weak-linked by Xcode the way other frameworks (such as Combine) are.This change also adds an
@availableguard on theDevMenuPresentationContextProviderprotocol, to ensure that calling apps using the DevMenu are properly guarding their own code with availability checks or a sufficiently high minimum deployment target.By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.