This makes sense. I currently work on an SDK team and we wrap this API, so naturally we like to follow the pattern of the underlying iOS framework so that it feels familiar to our customers. I am curious if this is an architectural decision? We do want to offer async/await in our APIs wherever possible, but we aren't sure if waiting on information contained in the redirect URL is better suited for the callback pattern instead of async/await since we're technically waiting on user input and not necessarily a concurrent operation.