We have hundreds of our customers calling in complaining that their reader keeps disconnecting and they have to re-pair device. Sometimes even having to forget the connection (bluetooth) and reconnect.. Not sure if this is reader-sdk issue or something else. We use the original SDK, not the new one. Does anyone else have any issues? @Bryan, how can someone from square help us investigate? We have over 400 customers complaining.
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
Reader SDK
Pair and Manage Card Readers
Pair and Manage Card Readers
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.
What is the application ID location_id and the timestamp of a disconnect? Also what changed? Did something update? Was there a firmware update or any sort of a version bump? Also what version of the SDK are you using? 
app: sq0idp-s6H6euU_XB-pZJwl3U4-uQ
location: 0YEV95P3CCD4X and V0058NJPB752X
timestamp: N/A reader disconnects when not in use and cannot catch the timestamp
sdk version: 1.7.4
Firmware updates automatically with clients so we can’t know when that happens but we are quite sure it happened. App is installed on ios 1.8.x. This is a problem with gen1 and gen2 devices. While disconnecting has been happening for long time, the problem is bigger now that when they try to pair device again it stays in “connecting” state for ever. This happens even when we delete our app and reinstall it and then try to pair. What works sometimes is to disconnect the reader and force close the app but some clients have to do that 2 - 3 times per day. We were able to reproduce it but no helpful logs are shown. Please see the image…there is SQUIActivity mentioned
Wow, that a really old version of the SDK. Have you looked at moving to a newer version of the SDK and moving to Mobile Payments SDK?
We’re planning to be moving to mobile payments sdk before year end but that’s about 4 weeks effort. We need the a faster solution for now to stop the bleeding. What is the latest reader-sdk version that we can update and avoid these issues and that doesn’t require a lot of code change? I believe you will stop supporting the reader-sdk at the end of the year. BTW, we are also using flutter plugin provided by you…that is on 4.0.1.