All Versions
75
Latest Version
Avg Release Cycle
47 days
Latest Release
4 days ago

Changelog History
Page 1

  • v5.0.2

    February 23, 2020

    🚀 Released on 2020-02-23. All issues associated with this milestone can be found using this filter.

    🛠 Fixed

    • 👍 Swift 5 support for AlamofireExtension.

  • v5.0.1

    February 23, 2020

    🚀 Released on 2020-02-23. All issues associated with this milestone can be found using this filter.

    ⚡️ Updated

    • AlamofireExtension to have public properties and initializer, and conform to @dynamicMemberLookup.

  • v5.0.0

    July 30, 2019

    Released on 2019-07-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

    • URLEncodedFormEncoder.DataEncoding and URLEncodedFormEncoder.KeyEncoding to customize the encoding of Data and CodingKeys in URLEncodedFormEncoder.
    • Asynchronous cURLDescription method to produce cURL commands for Requests which are in the process of creating their initial URLRequest.

    ⚡️ Updated

    • 📚 All inline API documentation.
    • Handling of response serializers appended after a Request has completed. This no longer produces an error but will instead trigger the normal Request lifetime methods.

    🛠 Fixed

    • Empty parameters being encoded as an empty String instead of nil by URLEncodedFormEncoder.
    • Handling of os_unfair_lock to prevent rare crash.

  • v5.0.0-rc.3

    October 27, 2019

    Released on 2019-10-26. All issues associated with this milestone can be found using this filter. Note: Alamofire 5 is now API stable.

    ⚡️ Updated

    • Automatic resume() behavior to be called after the first response handler is added instead of immediately after task creation.

    🛠 Fixed

    • 📚 Incorrect header convenience method in Usage documentation.
    • Unstable parameter ordering in URLEncodedFormEncoder.
    • 🏗 Xcode build issues and precompiled binary build issues by removing the dynamic bundle identifier.
    • 🏗 Build warnings for deprecated SecTrust API when building for Catalyst.
    • Regression from Alamofire 4 causing Alamofire to reject NTLM and Negotiate authentication methods.

  • v5.0.0-rc.2

    September 08, 2019

    Released on 2019-09-08. All issues associated with this milestone can be found using this filter. Note: Alamofire 5 is now API stable.

    🛠 Fixed

    • Single remaining use of Error instead of generic Failure constraint in DataResponse API.

  • v5.0.0-rc.1

    September 04, 2019

    Released on 2019-09-04. All issues associated with this milestone can be found using this filter. Note: Alamofire 5 is now API stable.

    ➕ Added

    • cancelAllRequests method on Session to cancel all in flight requests.
    • Ability to inject FileManager instance into UploadRequest.
    • DataPreprocessor protocol and implementations, allowing the preprocessing of data before serialization.
    • Internal URLRequest validation and error. GET requests with body data will now produce an error.
    • Generic Failure constraint to DataResponse and DownloadResponse, making them DataResponse<Success, Failure: Error> and DownloadResponse<Success, Failure: Error>.
    • 👍 Precondition to ensure Session can't be used with background URLSessionConfigurations. Alamofire will explicitly support such functionality at some point in the future.
    • ⚡️ SwiftFormat configuration and updated styling.
    • AFDataResponse<Success> and AFDownloadResponse<Success> typealiases to help deal with the doubly generic responses.

    ⚡️ Updated

    • All internal Result usage to use the fully qualified type instead of AFResult.
    • DataRequest and DownloadRequest functional API, renaming flatMap to tryMap.
    • HTTPMethod to be a struct rather than an enum.
    • 0️⃣ All errors produced by Alamofire to be AFError by default. All responses will now start with an AFError Failure type.
    • NetworkReachabilityManager to simplify and modernize its API.
    • 📚 Usage.md documentation to be fully up-to-date with Alamofire 5.
    • Bundle identifiers to include the platform name, fixing ITMS-90806.

    🛠 Fixed

    • Thread-safety issue with serialization queue usage.

  • v5.0.0-beta.7

    July 30, 2019

    Released on 2019-07-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

    • URLEncodedFormEncoder.DataEncoding and URLEncodedFormEncoder.KeyEncoding to customize the encoding of Data and CodingKeys in URLEncodedFormEncoder.
    • Asynchronous cURLDescription method to produce cURL commands for Requests which are in the process of creating their initial URLRequest.

    ⚡️ Updated

    • 📚 All inline API documentation.
    • Handling of response serializers appended after a Request has completed. This no longer produces an error but will instead trigger the normal Request lifetime methods.

    🛠 Fixed

    • Empty parameters being encoded as an empty String instead of nil by URLEncodedFormEncoder.
    • Handling of os_unfair_lock to prevent rare crash.

  • v5.0.0-beta.6

    April 24, 2019

    Released on 2019-04-23. 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.

    ⚡️ Updated

    • ServerTrustEvaluation logic by simplifying public key equality checks for SecKey types.
    • ⚡️ Request.State access to lock access and task updates using internal locking API.

    🛠 Fixed

    • Issues in DownloadRequest where some events were being duplicated and some were missing.
    • 🚀 Issue with AppStore submissions where the pre-release version in the bundle short versions string was being rejected when built with Carthage or as a submodule.
    • Issue where response serializer completions were not called when appended to a completed Request.

  • v5.0.0-beta.5

    April 13, 2019

    Released on 2019-04-12. 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

    • Request.didResumeTaskNotification, Request.didSuspendTaskNotification, Request.didCancelTaskNotification, and Request.didCompleteTaskNotification notifications.
    • Separate URLSessionTask lifetime events to EventMonitor.

    ⚡️ Updated

    • SessionStateProvider to no longer be public and renamed the file it lives in.
    • MultipartUpload to no longer be public.
    • 👍 Request, DataRequest, UploadRequest, and DownloadRequest to longer be open, as Alamofire does not support subclassing these types.
    • Names of the notifications posted by Request to include Notification.
    • httpHeaders extensions on URLRequest, HTTPURLResponse, and URLSessionConfiguration to be headers instead.

    🛠 Fixed

    • Issue in Request where calling cancel() inside a response serializer would result in the serializer running again.
    • Issue in Session where the delegate precondition would be triggered when running with a swizzled URLSessionDelegate.
    • Compiler error in the example app.
    • Issues Request where certain lifetime events could be triggered more than once by repeatedly calling resume(), suspend(), or cancel().
    • 🚀 Framework version string to be compatible with TestFlight and AppStore releases.

  • v5.0.0-beta.4

    March 29, 2019

    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.
    • The ability to retry requests after encountering response serialization errors.

    ⚡️ Updated

    • The switch and DispatchQueue logic throughout codebase to simplify usage patterns.
    • The MultipartFormData data APIs by condensing them using optional parameters.
    • 👍 The upload APIs for MultipartFormData to support custom boundaries.
    • 📦 The Xcode project, source code, SPM package, and podspec to support Swift 5 only.
    • 🚚 The Alamofire Result type to be a new AFResult typealias on the new Swift.Result type in Swift 5 and removed all public extensions.

    🛠 Fixed

    • Issue in RequestInterceptor closures where callback arguments were not marked as @escaping.
    • Issue in response serializers where emptyResponseAllowed logic was not working as expected.