Update submitApplePay so that shippingAddress isn't mandatory #2
Conversation
This file contains hidden or 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
…tion is not nil (previously could be nil if the user doesn't ask the user for shipping info).
Member
|
Thanks for the PR @tomhall - our lead iOS dev is away for a month unfortunately, but I will ask him to review when he returns. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Currently, as a consumer of the eWay iOS SDK, when using Apple Pay, you must specify
requiredShippingAddressFieldsof yourPKPaymentRequest, even if your payment doesn't need to capture shipping information. Failure to do so will result in an S9995 error due to theCustomerproperty ofTransactionbeing nil, which is required.This change ensures the
Customerproperty ofTransactionis never nil, so that payments without shipping information can be successfully processed.