-
Notifications
You must be signed in to change notification settings - Fork 6
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
Fix Upload Retry Bug #436
Fix Upload Retry Bug #436
Conversation
throwable is HttpException -> { | ||
val smileIDException = throwable.toSmileIDException() | ||
if (smileIDException.details.code == "2215") { | ||
SmileID.api.prepUpload(prepUploadRequest.copy(retry = true)) |
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.
@jumaallan we're starting to have duplication of code, is it possible to extract what we have in common between products and reuse that, this is a good example of docv and biometric kyc doing the same thing
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.
We cannot abstract this code per se since we need this flow inside submit job scope - we also modify the previous request so we need to be in the same lambda to avoid passing request and response body back and forth
Do we need to worry about https://docs.usesmileid.com/further-reading/result-codes/error-codes 2314 ? |
No, we are taking care of a different error code here |
Story: https://app.shortcut.com/smileid/story/13456/fairmoney-issue-investigate-and-fix
Summary
A few sentences/bullet points about the changes
Known Issues
Any shortcomings in your work. This may include corner cases not correctly handled or issues related
to but not within the scope of your PR. Design compromises should be discussed here if they were not
already discussed above.
Test Instructions
Concise test instructions on how to verify that your feature works as intended. This should include
changes to the development environment (if applicable) and all commands needed to run your work.
Screenshot
If applicable (e.g. UI changes), add screenshots to help explain your work.