New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We鈥檒l occasionally send you account related emails.
Already on GitHub? Sign in to your account
MBL-1158: Set up correct URLs for OAuth authorization endpoint #1935
Conversation
// TODO: MBL-1159: Get required information from the callback; call mutation to login. | ||
} | ||
|
||
if featureLoginWithOAuthEnabled(), let session = OAuth.createAuthorizationSession() { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Moving this into the OAuth struct, I don't think we'll need any logic to live in LoginToutViewController
.
return session | ||
|
||
} catch { | ||
// TODO: Is there a way we can log/monitor these errors? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@scottkicks Do we have a method for log generic errors in iOS? In this case, I only expect this catch to happen if something really odd occurs, i.e. we fail to create a URL from a hardcoded string, or are unable to generate a hash.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Added this to our iOS sync agenda.
9653d70
to
e9e3bad
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I have no idea how error logging works in our codebase unfortunately, but looks good for now!
馃摬 What
This sets up the actual authorization URLs we will be using for OAuth, instead of the previous placeholder.
馃 Why
Now that the web change is live, we can start testing!