-
Notifications
You must be signed in to change notification settings - Fork 35
New issue
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
3D Secure is not working #5
Comments
Can you exactly tell me how to reproduce this behavior ? Can you please check whether you had added the redirecttcomponent in your swift file and other ios installation steps.... info.plist CFBundleURLTypes `` @objc class AdyenObjectiveCBridge: NSObject { @objc(applicationDidOpenURL:) |
If you call /payments api with "react-native": "0.61.4" Use this card: 5454 5454 5454 5454 |
Yes I have this redirect part in my app... |
@voslartomas - Just now I tested with Adyen Test Card for 3DSecure Autehntication |
Wow sweet, so it's something on my side, thanks. Btw thank you for this repo, great work. |
I had bumped the ios adyen sdk with 3.3.0 now and released a new version.Please update and check. |
Still same... |
What is this part about '3 . Configure info.plist with CFBundleURL for redirect URL in the PaymentData' ? Can you show me your example? |
@voslartomas -Is the issue resolved ? |
Not solved yet I am getting this error.
|
@voslartomas - Can you open this in a different thread because it's a different issue in the API response |
@mkharibalaji It might be different issue, but it's still regarding 3DS, do you still want me to open another thread? This is not happening in normal payments without 3ds. |
@voslartomas - Did you check "application/json" as content type in response headers from your server because this error usually comes when your response is not in JSON format or ContentType not set properly. |
@mkharibalaji Hi, when there is action in response, it should handle 3d secure authorization, but in app I can see only loader on button. Did you encounter this behaviour?
The text was updated successfully, but these errors were encountered: