AppAuth-iOS relies on a series of categories to provide callers with the ability to perform an authorization flow. These categories require a UIWindow or UIViewController to be passed in as the presenting context for the flow.
This requirement works fine for callers operating within a UIKit or AppKit framework, but is awkward in SwiftUI, where developers do not directly create and password UIWindows or UIViewControllers.
The goal of this work is to provide new functionality to AppAuth-iOS that will not require a presenting window or view controller. Instead, these new methods will attempt to automatically find a suitable window or view controller on the developer's behalf. While the motivation for this work is to provide SwiftUI developers with a more natural API for starting an authorization flow, the result of this work should equally serve UIKit and AppKit developers as well.
List view
0 issues of 4 selected
- Status: Open.#739 In openid/AppAuth-iOS;
- Status: Open.#740 In openid/AppAuth-iOS;
- Status: Open.#741 In openid/AppAuth-iOS;
- Status: Open.#742 In openid/AppAuth-iOS;