search

Adyen / adyen-ios

Adyen iOS Drop-in and Components
https://docs.adyen.com/checkout/ios
MIT License
151 stars 122 forks source link

error code 702 "java.io.IOException: Unexpected end of stream" in 3DS2 #794

Closed tw-manishp closed 6 months ago

tw-manishp commented 2 years ago

Describe the bug When we make payment using 3DS2 test cards with correct card number and wrong cvv and wrong expire date, then when we handle the action object it gives "java.io.IOException: Unexpected end of stream" in between. Sometime it opens the 3DS2 screen but sometime it throws the above error

To Reproduce

  1. Fill the 3DS2 card details, correct card number and wrong cvv and expire date
  2. Click on submit button
  3. At this step you must see error. if 3DS2 screen is open add correct code 1234 and click submit
  4. Repeat above process until error is generated

Expected behavior It must open 3DS2 screen every time

Screenshots

Screenshot 2022-02-10 at 9 27 06 PM

Smartphone (please complete the following information):

Additional context We are using Adyen 4.2.0 SDK

descorp commented 2 years ago

Hey @tw-manishp

Unfortunately, I wasn't able reproduce it.

Repeat above process until error is generated

How many times you usually have to repeat it until error occur?

tw-manishp commented 2 years ago

Sometime it happens at first attempt. Sometime it happens on 3rd,4th,... etc attempts.

If we can schedule a call or i can share action object or screen recording

On Mon, Feb 14, 2022, 22:19 Vladimir Abramichev @.***> wrote:

Hey @tw-manishp https://github.com/tw-manishp

Unfortunately, I wasn't able reproduce it.

Repeat above process until error is generated

How many times you usually have to repeat it until error occur?

— Reply to this email directly, view it on GitHub https://github.com/Adyen/adyen-ios/issues/794#issuecomment-1039313940, or unsubscribe https://github.com/notifications/unsubscribe-auth/AUGX3GSS7R4MZLUOPD36DYLU3EXDFANCNFSM5OBF7VKQ . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

You are receiving this because you were mentioned.Message ID: @.***>

descorp commented 2 years ago

What Adyen API version are you using? This happens on TEST, LIVE or both?

Could you share a pspReference of a failed attempt? You should be able see one in the header of the /payments response

sinanabusmoda commented 2 years ago

We are using Adyen 4.2.0.

This is observed both in TEST and LIVE, Europe. Upon observing in the LIVE, we implemented a retry mechanism and it is able to render in the 2nd attempt most likely in a failure scenario.

Due to architectural limitations, we are not able to observe the pspReference for a failed scenario in LIVE. We can figure it out for TEST environment, Idk if this could be helpful to track.

descorp commented 2 years ago

We are using Adyen 4.2.0.

I mean Adyent API version

We can figure it out for TEST environment, Idk if this could be helpful to track.

Any pspreference of a failed payment attempt will be very helpful.

we implemented a retry mechanism and it is able to render in the 2nd attempt most likely in a failure scenario.

It is recommended to always retry networks calls on iOS. In specific cases (e.x. when app leaves foreground) previous session could be corrupted..

kightsonsanom commented 2 years ago

Hello, I am able to reproduce the issue. The difference is that all the card data are correct. We are currently in development phase so it was only tested on TEST environment. I am using:

descorp commented 2 years ago

Hey @kightsonsanom

Thanks for pspReference! Seems like 3DS2 Fingerpring is extremely large for some reason..

Can you easily reproduce it? What are the steps?

kightsonsanom commented 2 years ago

@descorp unfortunately this is not easily reproducible, sometimes in happens a couple of times in a row though. I don't know the exact steps but I was able to reproduce this only with American Express cards such as this one:

American Express 3714 4963 5398 431 03/2030 7373
Alexia-iordanoglou commented 2 years ago

hey @tw-manishp @sinanabusmoda Did you manage to solve the bug?

Alexia-iordanoglou commented 2 years ago

@descorp Do you have any more info on this bug?

descorp commented 2 years ago

Hey @Alexia-iordanoglou

No update so far. We started internal investigation. Current theory is that payment data become too big. This issue occur on different flows and not (yet) deterministic.

Will keep you posted.

goergisn commented 6 months ago

Closing due to inactivity. Please feel free to re-open the ticket.