Cannot Connect Square reader using mobile payments sdk

Questions
1

I have implemented the ios react native plugin for the Square Mobile Payment SDK and am currently using a production App ID. While attempting to connect the Square Reader through the Square settings screen, I receive a “Reader pairing successful” message; however, it is followed by the error:

“Reader unavailable: Unable to establish a secure connection to Square.”

From my end, I have already:

  • Updated the app signature (SHA-256) on the Square Dashboard

  • Activated the Square account

I didnt modify the sdk in anyway. This happened 2:24 AM (05/17/26). Could you please confirm if any additional setup or configuration is required to resolve this issue?
Timezone: EST
App ID: sq0idp-PmI6CXKFXkfoou5Q22JIDg
Location Id: L0P18VSSEXCYV
SDK Version: 2.5.0

2

:waving_hand: 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:
https://developer.squareup.com/docs/reader-sdk/react-native
https://developer.squareup.com/docs/reader-sdk/cookbook/contactless-reader

Additional Documentation

https://developer.squareup.com/docs/reader-sdk/build-on-ios
https://developer.squareup.com/docs/reader-sdk/cookbook/square-stand
https://developer.squareup.com/docs/reader-sdk/quick-start/step-2

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

@anikal2001 Thanks for providing all those details here! I’ve escalated this to the team.

4

@anikal2001 Are you able to verify that you have the correct app signature for the build you have installed?

5

Yes, i believe the app signature is correct

6

@anikal2001 The behavior you’re seeing really only happens when there’s an issue with the app signature. For context, it’s possible for each build you generate to have a different app signature, so you’ll need to make sure that your app signature being generated is the same across all debug and release builds.

To troubleshoot, I’d recommend:

  1. Try to get the app signature from an APK.

  2. Make sure that app signature matches what’s in your developer console.

  3. Try to install that APK and see if your error still persists

7

I am building an IOS app

8

Hey @anikal2001, we had a similar report for this issue (on both iOS and Android) here:

Can you take a look to see if that helps for your case as well?