Alamofire: Concurrency Crashes Using Xcode 13.2/.1 and Bitcode Issue on Xcode 13.3
Launch times for models below iOS13 libswift_ Concurrency.dylib (which was built for iOS 13.0), because ‘5.5.0’ supports Concurrency, but only supports models above iOS 13. Please limit the usage environment of Concurrency
About this issue
- Original URL
- State: closed
- Created 3 years ago
- Reactions: 4
- Comments: 21 (9 by maintainers)
I have run into the same issue, solved by pod ‘Alamofire’, ‘5.4.4’
@gabors Thanks for confirming! Bumping the required Swift compiler for the concurrency features is up as #3590, so this should get merged and released soon.
@gabors Alamofire 5.4.4 should work fine, as it doesn’t include any concurrency code. Unfortunately Xcode 13.3 has it’s own concurrency bug where any inclusion of concurrency code will break BitCode processing when deployed back to iOS 13 or 14. You can turn off BitCode, keep using Xcode 13.2.1 (and deal with its bugs), or keep using Alamofire 5.4.
I’ll open a separate issue to track the BitCode problem but since it seems like Apple can’t fix these issues I’ll likely have to separate out the concurrency code into its own subspec (for CocoaPods) or module (for SPM). Carthage users are likely out of luck.