Compact Unwind Warnings on watchOS #3083
Merged
Conversation
This file contains 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
jshier
approved these changes
Feb 26, 2020
|
We certainly could. Do we have a good place to track that now? Maybe a section next to open radars? |
|
Seems like a good place. A “workarounds” or something similar section? |
|
I'll add the note as part of the next release. |
|
Getting ld: -no_compact_unwind and -bitcode_bundle (Xcode setting ENABLE_BITCODE=YES) cannot be used together when trying to archive Alamofire 5.0.3 for watchOS. I think it caused by the changes added in this pull request. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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 Link 🔗
I'm seeing compact unwind warnings on watchOS with Xcode 11.3.1.
Goals ⚽
To eliminate the compiler warnings on watchOS.
Implementation Details 🚧
The only solution I've been able to find over the past year or so when this occurs is to disable the compact unwind warnings themselves. If anyone else has more information on how to resolve this properly, I'm all ears. We've done this on some of our internal project and haven't run into issues due to disabling them yet.