I’m trying to migrate my app from the readerSDK to mobile payments SDK after discovering the readerSDK is not connecting on android 16
when i go to the square dashboard to add an app signature for android, it is not accepting any attempts to add a SHA-256 certificate
I’ve tried generating it, I’ve tried getting the certificate from the google play console. I’ve tried formatting a few ways. Just the same generic error with no further information every time
very frustrating for the readersdk integration to break months before the deadline to transition to mobile payments and the mobile payments integration to not be a smooth easy process. Is there any specific formatting that needs to be done for the SHA-256 certificate or any way to get more information on why its getting rejected?
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 Quickstart
Build on Android: Reader SDK
Square Developer
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.
I see you also added to another post. Looks like the format is the issue. It needs to be hexadecimal string without any colons. For example:
e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855
gotcha, ill give that a shot, thanks!
Okay this worked after i removed the colons AND made it all lowercase
the way most developers are going to retrieve this will be either from the google play console where its full caps and colon delineated or keytool generated which iirc is also full caps and colon delineated
maybe y’all should consider accepting it that way to avoid confusion for users or at the very least adding a warning message if you detect colons or capital letters