Well, we store the token in ios flash and by debugging we found everytime we DID passed the correct token saved last time.I assume this is local debugging, not production? Do you have production logs that verify your claim? It sounds like you have an ios based POS, and are storing the tokens locally. The most likely explanation is that the tokens are being removed or they are not being passed correctly.
Regarding the maintaining connection. Could you tell me more about it. Right now we just initialize the connection once when first time access the clover device and keep the instance in static class.It sounds like you are managing the connection correctly.
Is this a new problem or something you have seen for quite some time? What device types?
I think my question is if the clover network pay app communication is actually disconnected due to long time no ping response from our ios app (in sleeping mode), then when our ios app wake up and call the auth/sale over the original cloverconnector instance, WILL it trigger the "paring" process ?The pairing process SHOULD NOT be triggered in this situation (assuming our previous discussion about you passing the correct token). If you are seeing the pairing screen I would consider this a bug. That being said both Secure Network Pay Display and the iOS SDK are widely used and I do not see any external or internal reports mentioning this or similar problems.
2 People are following this question.