-
Notifications
You must be signed in to change notification settings - Fork 122
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’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
COIOS-812: Identify native redirect flow (v4) #1886
base: v4
Are you sure you want to change the base?
Conversation
|
||
|
||
/// Redirect type. | ||
public let type: RedirectType |
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.
Leaving this comment to not forget the conversation we had regarding the backend behavior
@@ -1,5 +1,5 @@ | |||
// | |||
// Copyright (c) 2022 Adyen N.V. | |||
// Copyright (c) 2019 Adyen N.V. |
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.
Different swiftformats fighting each other again
Quality Gate passedIssues Measures |
Summary
This development enables us to differentiate between regular and native redirects. To handle cases where native redirects fail (indicated by
nativeRedirectData
beingnil
), it's essential to track the originating flow type of each redirect.Motivation
Native redirect flows can occasionally fail if
nativeRedirectData
isnil
within the action object. Currently, we handle this by discarding the native redirect (checking ifnativeRedirectData
is nil), and defaulting to a "direct issuer flow" using a/details
call.To avoid the additional steps of the "direct issuer flow," we can address this issue on the backend. By identifying the native redirect flow, we can still retrieve the native redirect result directly.
Release notes
Ticket
COIOS-812