Skip to content
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

Timeout error immediately after detecting card swipes #84

Open
iamjayanth opened this issue Aug 6, 2021 · 0 comments
Open

Timeout error immediately after detecting card swipes #84

iamjayanth opened this issue Aug 6, 2021 · 0 comments

Comments

@iamjayanth
Copy link

We are using the In-Person SDK for our Android app for swipe transactions. And we use BBPOS Chipper 2x swiper. And we use bluetooth for connection. The Android model is Samsung Galaxy A42 5G running Android 11.

And some of our end users ran into an issue when using the swiper in a box office terminal. The swiper was connected and has done multiple card transactions continuously for around 3-4 hours without any issue. The swiper was also connected to the power because they didn't want the battery to get low in the middle of the event.

But after some time, the swiper started to throw timeout errors when swiping cards. As per their report, the screen asking for a card to be swiped was shown (indicating swiper got connected with the SDK). But as soon as the cards were swiped, the card transaction screen was closed and the app received a timeout error. Based on the error message shown in the app (they sent us a screenshot), we understood that following method got fired with error code EMVErrorCode.TIMEOUT

override fun onEMVReadError(errorCode: EMVErrorCode?) {}

From this moment on, the swiper threw a timeout error for every card swipe causing the entire terminal to be non-functional resulting in a long queue. The operator there removed the power supply from the swiper, Switched it OFF and then ON, paired with the mobile again and the swiper started to work. 

So, what we would like to know is why the SDK returned a timeout error in this instance. We couldn't find any API reference or documentation about when/why these errors are thrown. The timeout is a weird error because it was thrown immediately after detecting a swipe (there was absolutely no delay). 

Let us know if any other information is needed. 

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

1 participant