Open ahmetgsu opened 2 years ago
Hey @ahmetgsu
Thanks for reaching out!
At the moment - this is intended behaviour of our SDK. All our Components never un-blocking themselfs and intended to be a "one-time" operation:
Thank you, @descorp, for your prompt reply.
One can continue the transaction without hiding the CardComponent
on Android after the CVV declined
message.
Is this a kind of bug in that case?
I am afraid this is a simple misalignment between iOS SDK and Android SDK 😅 I will follow on this with Android team, will keep you posted
Thanks for your feedback @ahmetgsu 💚 This is a main reason we started React Native support project - to even this kind of misalignments..
Hey @ahmetgsu
As for beta-7
and future beta-8
there would be no option to dissmis/stop "loading" after didSubmit
is triggered.
Sorry for mis-information.
This behaviour is available on iOS DropIn, but not supported no Android DropIn. Previously (up to beta-4) Card Component on Android was using custom implementation, but currently it is utilising a DropIn. To enable it, we have to wait till Android DropIn supports it (expected on v5)
We are trying to implement the Adyen DropIn for
Preauthorization
on our React Native project.When the resultCode is
Refused
due to the wrong CVV or an issue with the expiry date of the card, we dismiss the DropIn and display the error message. We tried not to dismiss the DropIn and only show the error message on the screen for that specific case to prevent the users from re-entering the same card information. However, the spinner never ends, and the input fields are not interactive.Is there any way to stop the spinner without closing the DropIn?