Alamofire VS Moya

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

Alamofire - Alamofire is an HTTP networking library written in Swift. (de facto standard library for network) Language: Swift.

In terms of dependencies, I always use Moya. It's a bit heavy, and it's not perfect, but holy hell is it better than nearly every networking layer written "from scratch" I've seen on nearly every project I've worked on. It's amazing to organize requests in a predictable way, have testing baked into the framework, and has first-class support for RxSwift/Combine. I can't recommend it enough.

Friends who are familiar with swift should know an excellent three party library Moya, the plugin version of the network request is really fragrant, so I use the idea to make a pure oc version of the plugin Network request library.

Moya - Network abstraction layer written in Swift. Language: Swift.

What is the advantage of your library over established solutions like Moya or protocol oriented networking approaches?