Fix transfer asset loading issues on iOS with static typing #733
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
jaredvu
reviewed
Oct 29, 2024
Comment on lines
-47
to
-50
| if (type == null) { | ||
| val error = ParsingError.cannotModify("type") | ||
| return StateResponse(state, null, iListOf(error)) | ||
| } |
There was a problem hiding this comment.
are we removing because because type can be null?
There was a problem hiding this comment.
Yeah.. iOS is passing null there
jaredvu
approved these changes
Oct 29, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
When iOS passes in transfer.type == nil, Abacus should still set the inputType to "transfer" so that the transfer assets get assigned to the transfer.input.