Contactless reader failed to connect

Questions
1

I am having difficulty pairing readers with the mobile payments sdk on android.

I have tried both a starter application written by myself using SDK version 2.0.1 and the quickstart application using SDK version 2.0.0-beta5.

When attempting to pair a reader using the SDK’s settings menu, the entire process goes smoothly until after the “success” is shown with a green check mark. When the pop up closes and shows the list of devices, the reader will just say “failed to connect”. I can see all of the information for the reader by selecting the device and I am able to use the identify reader feature.

So far when this happens I am not seeing any errors in logcat or debug.

2

:wave: I’m Square Dev AI, here to help answer your question!
Based on the information you’ve provided, the following documentation will help answer your question:

Additional Documentation

Build on Android: Reader SDK
Configure the Reader SDK Sample Application
Connect a Contactless Reader

If this documentation helped you find a solution, please check the box indicating that this reply solves the problem.
Otherwise one of our Developer Advocates will provide additional assistance shortly.

3

What troubleshooting have you done with the device? Have you restarted the reader? :slightly_smiling_face:

4

Yes, we have sorted the issue out here as far as I have been able to test.

I went through all of the troubleshooting recommended and had no luck.

Another developer implemented the Reader SDK on the same device. We were able to pair a reader using that. Ever since, any other readers we have all connect using the Mobile Payments SDK without any issues. I am unsure why this might be, but it is working now.

5

Was there times when you had two of the Square SDKs on a device? Maybe both were conflicting with each other? :slightly_smiling_face:

6

Not while the issue was ongoing, it only began to work once they had both been used on the same device. This tablet had a fresh OS install before testing the Mobile Payments SDK and encountering the issue with pairing.

7

If there are two SDKs involved that has been known to cause issues. We definitely recommend having only one on the device. :slightly_smiling_face:

8

That would make sense. There is only one on the device now, which is the Mobile Payments SDK. It is all working as expected now, we just do not have a conclusion as to why readers would not connect pre testing the Reader SDK.

9

Glad to here that it’s working as expected now. :slightly_smiling_face: