Alamofire VS AFNetworking

I don't have any numbers, but I think this is still pretty common. On iOS for example Alamofire which is a popular network stack, still offers this as a feature. I think the use case is a bit different for apps and web sites, especially for closed ecosystems like Apple's where reverse engineering is not as easy/straightforward.

https://github.com/Alamofire/Alamofire

let package = Package( name: "YourAwesomeApp", dependencies: [ // Add your own dependencies here: // .package(url: "https://github.com/Alamofire/Alamofire", from: "5.0.0"), // You can read more about dependencies here: https://docs.tuist.io/documentation/tuist/dependencies .package(url:"https://github.com/RevenueCat/purchases-ios-spm.git", .upToNextMajor(from: "5.0.0")) ] )

To access the APIs, you need an API key, which which you can get with the free Basic plan. Once you have it, authorization is via a Bearer token making it easy to create a simple wrapper client using Alamofire.

Alamofire is a swift http request lib. By default, we need use completion handler to handle response. Today we are going to find out how to use it with async and await.

Looks like your Alamofire tutorial is out of date. I suggest you read the current documentation and update your code. For instance, you can update your example to:

Alamofire - Elegant HTTP networking

AFNetworking - A delightful networking framework. Language: Objective-C.