Open eeynard opened 7 months ago
Ran into the same thing today when canceling discoverReaders
. There's a clear workaround to handle both but would be nice to be aligned.
Wait so you guys are using tap to pay with react native all from this library? Do you use expo?
Describe the bug After calling
collectPaymentMethod
, the TapToPay UX appears and if the user cancel the payment, we receive different error codes depending on the platform :{ code: 'Canceled' }
as described in the enumCommonError.Canceled
so that's ok 👍🏻{ code: 'USER_ERROR.CANCELED' }
=> should it beCommonError.Canceled
too ?To Reproduce Steps to reproduce the behavior:
Expected behavior Android Only : The error code returned when the payment is canceled should be
Canceled
(enum:CommonError.Canceled
) and notUSER_ERROR.CANCELED
Screenshots N/A
Stripe Terminal React Native SDK version
Smartphone (please complete the following information):
Additional context N/A