Mobile Payments SDK - Unable to establish secure connection to Square error in Android .aab build on Play store

I am in the process of publishing an Android version of an app that uses the React Native Mobile Payments SDK, and have run into an issue with card readers connecting to the Square servers. When I run a signed APK locally, the readers connect to Square with no issue and I can run transactions. However, when I upload a signed .aab build to the play store and try to use it in closed testing, I get the “Unable to establish secure connection to Square” error in the device management section for both Tap to Pay and physical card readers. This issue persists whether developer mode is on or off.

Both builds should be identical, other than one being an app bundle and one being an apk. Are there known issues with connection requests from beta tests on the play store? Before review, my app was listed as “com.merchcast.register (untested)” which I thought might create issues, but since it has been reviewed the package name seems to be correct.

I wound up resolving this myself. For others who have this issue in the future, I had to go into my Google Play developer settings and add the signing key SHA 256 signatures that had been automatically generated by google.

1 Like