We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Describe the bug on device tip amount returns null on ios instead of returning the amount entered on the reader device
To Reproduce Steps to reproduce the behavior:
"amountDetails": { "tip": { "amount": null } },
Expected behavior I would expect the tip amount to be returned under amountDetails.tip.amount
amountDetails.tip.amount
Screenshots If applicable, add screenshots to help explain your problem.
Stripe Terminal React Native SDK version
^0.0.1-beta.22
Smartphone (please complete the following information):
Additional context I was looking at the ios code here and I think this should be:
class func mapFromAmountDetails(_ amountDetails: SCPAmountDetails?) -> NSDictionary { let amount: NSDictionary = [ "amount": amountDetails?.tip?.amount ?? NSNull(), // need to add ?.amount ] let result: NSDictionary = [ "tip": amount ] return result }
The text was updated successfully, but these errors were encountered:
Thanks for your voice and we'll fix it in the next release.
Sorry, something went wrong.
tim-lin-bbpos
No branches or pull requests
Describe the bug
on device tip amount returns null on ios instead of returning the amount entered on the reader device
To Reproduce
Steps to reproduce the behavior:
Expected behavior
I would expect the tip amount to be returned under
amountDetails.tip.amount
Screenshots
If applicable, add screenshots to help explain your problem.
Stripe Terminal React Native SDK version
^0.0.1-beta.22
)Smartphone (please complete the following information):
Additional context
I was looking at the ios code here and I think this should be:
The text was updated successfully, but these errors were encountered: