question

etouchmenu avatar image
etouchmenu asked Raymond Lee Deactivated commented

PROBLEM | Sale App 1.0-140 | Keypad displays when inserting/swiping card |

Hello Clover support -

Problem
When inserting a card into the EMV reader or swiping a card, the Clover app called "Sale" v1.0-140 calling the following RECEIVE_CARD_INSERTED and RECEIVE_CARD_SWIPED.
When in SINGLE app mode, this screen does not have a way to escape from the keypad.
Steps
1. Insert card into Clover Mobile 3G (regardless of screen ie: setup)
* Key pad displays
2. Remove card
* Key pad remains on display
Sale
10 |2000
Toggle Comment visibility. Current Visibility: Viewable by all users

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

1 Answer

Raymond Lee avatar image
Raymond Lee Deactivated answered Raymond Lee Deactivated commented
The Sale app opening when a EMV card is inserted is intended by design. The fact that you cannot exit out of it, is due to your app enabling single app / customer mode, and not disabling it when your app is paused.
In your onPause() of your app's activity, you should disable customer mode, and then if you want to still be in single app / customer mode when you go back to your app, you can enable it again in your onResume().

For example: 
@Override
protected void onResume() {
    super.onResume();

    CustomerMode.enable(getApplicationContext());
}

@Override
protected void onPause() {
    super.onPause();
    
    CustomerMode.disable(getApplicationContext());
}

12 comments
10 |2000
Toggle Comment visibility. Current Visibility: Viewable by all users

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

etouchmenu avatar image etouchmenu commented ·

Hi Raymond - Thank you for the reply. Is this new functionality in >139 release? We are now seeing v.1.0-142 on the terminal where this was not available in the 1.0-139. Thank you

0 Likes 0 ·
Raymond Lee avatar image Raymond Lee etouchmenu commented ·

No problem! If you are asking when this CustomerMode functionality was available, it is part of our clover-android-sdk, so it is not tied to the version of the Sales app. According to our github repo, it has been available since Dec 2016. See:

https://github.com/clover/clover-android-sdk/blob/5c6a9de3ac5c3783153b13625c559f1014b46841/clover-android-sdk/src/main/java/com/clover/sdk/util/CustomerMode.java

0 Likes 0 ·
etouchmenu avatar image etouchmenu Raymond Lee commented ·

Good Morning Raymond - The question is more of version change in the 1.0-140 and above. In the video I have a 1.0-139 on the left and the 1.0-140 on the right side.

https://www.dropbox.com/s/oa0zi35rlsadg48/IMG_0331.MOV?dl=0

0 Likes 0 ·
Show more comments
etouchmenu avatar image etouchmenu commented ·
Thank you for the response Jeffery. For clarification purposes Raymond provided a workaround and the 1st level support gave a permission level work around that was not ideal as it shows an error message to the user. But you have identified this as a defect? Our CEO is monitoring this closely. Are there any additional workarounds we might be able to present?

Thanks for the assistance.
0 Likes 0 ·
Jeffrey Blattman avatar image Jeffrey Blattman ♦♦ etouchmenu commented ·

No, I don't have a workaround, re: stopping the Sale app from coming to the foreground when a card is inserted. Yes, I created an internal issue to come up with a solution to this.

0 Likes 0 ·
etouchmenu avatar image etouchmenu commented ·
Raymond,
Do we have a solution we can implement that will disable the native clover app. While you are saying it should have always been performing this way we do not want it to do so and would like the app not to be called at all when a card is inserted?

Thank you for the help.
-1 Like -1 ·
Jeffrey Blattman avatar image Jeffrey Blattman ♦♦ etouchmenu commented ·

No, there's no workaround for stopping to "start sale on dip / swipe card" behavior. We should provide an API for you to abort or otherwise respond to the events yourself. I've filed an internal issue to get this resolved. I cannot provide a timeline for a fix.

0 Likes 0 ·

Welcome to the
Clover Developer Community