Swift 5 and Response Serializer Retry Support

Released on 2019-03-29. All issues associated with this milestone can be found using this filter. Note: Alamofire will not be following semantic versioning during the beta process. There may be breaking changes until 5.0.0 is released.

Added

• The AlamofireExtended protocol and used it to namespace all public extensions.
  • Added by Jon Shier in Pull Request #2758.
• The ability to retry requests after encountering response serialization errors.
  • Added by Christian Noon in Pull Request #2716.

Updated

• The switch and DispatchQueue logic throughout codebase to simplify usage patterns.
  • Updated by Joan Disho and Christian Noon in Pull Requests #2691 and #2765.
• The MultipartFormData data APIs by condensing them using optional parameters.
  • Updated by Ernesto Rivera in Pull Request #2766.
• The upload APIs for MultipartFormData to support custom boundaries.
  • Updated by Christian Noon in Pull Request #2764.
• The Xcode project, source code, SPM package, and podspec to support Swift 5 only.
  • Updated by Christian Noon in Pull Request #2771.
• The Alamofire Result type to be a new AFResult typealias on the new Swift.Result type in Swift 5 and removed all public extensions.
  • Updated by Dave Camp, Eric Jensen, and Christian Noon in Pull Requests #2769 and #2774.

Fixed

• Issue in RequestInterceptor closures where callback arguments were not marked as @escaping.
  • Fixed by Scott Talbot in Pull Request #2747.
• Issue in response serializers where emptyResponseAllowed logic was not working as expected.
  • Fixed by Jon Shier in Pull Request #2772 in Regards to Issue #2770.