OAuthSwift VS Alamofire

Edit: they did say it works with discord in a question someone asked here https://github.com/OAuthSwift/OAuthSwift/issues/597

https://www.raywenderlich.com/243-oauth-2-0-with-swift-tutorial and subsequently OAuthSwift Im still pretty lost on all of this. Do I really need to use a proxy if I can save the app token to the keychain?

Also, there are already OAuth frameworks available, like OAuthSwift. Use what's out there instead of reinventing the wheel, unless absolutely necessary.

I would recommend reading the docs (and maybe source) of https://github.com/OAuthSwift/OAuthSwift and reading the docs on Google’s OAuth implementation. Avoid the ones they have that depend on using their SDK, but look for the web ones instead.

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.

You can find an example using Alamofire, the most commonly used network framework, here.

https://github.com/Alamofire/Alamofire/blob/master/Documenta...

To add Alamofire, we'll be using Swift Package Manager. Xcode comes with built-in support for it and we'll not have to use external package managers like Cocoapods or Carthage. Click on File → Add Packages...