-
Notifications
You must be signed in to change notification settings - Fork 32
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
Advanced flow + Android: Additional details not being handled (Expo) #536
Comments
Hey @zegenerative Could you provide more details:
|
|
I see. On Android, the Drop-In is an Activity with its own unique The appropriate As alternative, you can get Drop-in import {AdyenDropIn} from '@adyen/react-native';
const returnUrl = Platform.select({
ios: ENVIRONMENT.returnUrl,
android: await AdyenDropIn.getReturnURL(),
}); |
I implemented the returnUrl based on device by But it didn't work. On iOS the additional details are triggered, everything is fine. Android never reaches that point. Apparently it doesn't have anything to do with the returnUrl, since it does actually redirect, with the same url given as iOS. It just never triggers the additionalDetails on Android, as if it redirects to the app, but not 'to' the sdk. The log I was getting, was coming from a util that parses deeplinks. Could it be that state is lost during the redirect? And in case of iOS it is still present because of the webview instead of directing out of the app? Edit: and because of this, the onComplete is also not being called. Do I need to register the adyencheckout://etc url as a deeplink in our app? |
Hey @zegenerative
Drop-in Normally, you can find You can verify that you have the right one by opening any web redirect payment on DropIn and executing: adb shell am start -a android.intent.action.VIEW -d "adyencheckout://com.your.package_name" com.your.package_name Could you confirm with your backend team that the adyencheckout://com.your.package_name value you are using for Alternatively, you can reach out to our Support Team via Customer Area or via email: [email protected] and provide them with PSP reference (or link to the transaction in question). Please mention this thread, so they can provide this info directly to me. |
our returnUrl is I will check with our BE what the returlUrl is. The response however, is an object containing a redirectResult being
Our app is sending the following paymentMethodData: {"paymentData": {"amount": {"currency": "EUR", "value": 119370}, "paymentMethod": {"checkoutAttemptId": "cd480e8f-239a-4d40-8fe9-e225460b813c1728479587842CB4569689F3FB520DCB519F05FFB9328F364D7EA228CA0978EF2588B9F09AD7C", "type": "ideal"}, "returnUrl": "adyencheckout://nl.mywheels.app", "supportNativeRedirect": true}} If I execute your shell script with the package name updated, nothing happens. |
This look like Where do you see this?
You should be able to see result if you open |
Describe the bug
(Works on iOS)
On android, the additionalDetails callback does not seem to be triggered on redirect. Probably because on iOS you stay within the app in a webview, but on Android you redirect out of the app to a chrome browser window.
To Reproduce
Expected behavior
Drop in triggers callback(s)
Additional context
In our case we get this log, and I can;t see where it's coming from
/reservations/0192518f-af7a-740b-8e58-6c2d2aa0e6d6/payment?redirectResult=X3XtfGC9%21H4sIAAAAAAAA%2F31UXW%2FTMBT9L3nGwUmcOImEUL%2FYutJRui4dExJy7JslkDrGcYBq2n%2FH7gorQ%2FDW3Ht8ru85x733uAZmQIyMl3shDgkKMMLRBqc5oTlOb70XngbRaOBmxfY7kGbKDPPye4%2Fxr4Ot6xHn3SDNXHh5GgYhJi88tnMVB%2BKD1iD53rLPrteW7BtrB%2FDyICCYBg8WqpoCdN900stp4L5V23BmbGEuq%2B4wSOxBvm1KzfTefUu2swyPZaRqhSwHao99O%2BEXnd3Hj3zsPdgxtinFpBPuYCOAtRbIa%2BBfusFMaiYltLYzkkJ3jbC9HWhuy%2Ba4nO0t99saoO1PmmuowG3nSHGQhXGQVqgEHiMa4gqloUhQHFUpzuxPglN7tNPNXSNZu%2BrV6emzt4tNfE7DOE3XV4sitkjF2jX0Q2ueQYv1Kr6JVun2bDM9pweohq8D9Pauj4acommQ4jCiSRiRKKM0OEEL0TiVWfvb0D%2Bl94%2BSFs%2F1tCa1bfc9ml6Ftmi09fNJk7k0cKcPJP6TE4fB%2F%2BC%2F%2FL%2BdGpRNKOokMs0OrF3%2Fn2n2yrFNzmeTxbvrzaez2eVsPZ94D47JDFpea%2Bd0bYzq848vP778lYK%2B7pQCjYzVxj9cxufd7q%2F%2BU%2BH4HNYH1td3qhGvzlY4i9PROJpOw3RMx%2FHI3rKH1j4eEGMXwZP4HQnd5TXj5lGomZ3p1oInwLOUYSCMIBZyjihhAjFISyQSEhCSBREjLhD9l0Yew66G0v8W%2BosiLIrbi224WEZxXMT%2BuJ0t7dO80abva3O7%2FbFQ2edis82%2Ba8b6DZDogn7CGbu5cInvTafhuPASTN3ZRZwJp6qumGa73gVJ9WrG6%2B4xV38F9vgvke%2BXyZttizfvJRvefVhX9eo8KWhUvNnPXzm7jFUFFLOrO8sxRlxgWpEgiiuS0JIGjNE4LYMoKeOyIowjIZKEYl5BREhUZinCgffwEx2%2BRfjjBAAAiZKP6NCuXgpyIrI8K%2F%2BKcQ5IPGWM4p7VITgfa0Pmzd0%3D
The text was updated successfully, but these errors were encountered: