Error: SCPErrorAppleBuiltInReaderFailedToPrepare in Tap to Pay Connection

[AnshulMindbody]

Greetings,

Several users have reported encountering the SCPErrorAppleBuiltInReaderFailedToPrepare error while trying to use the tap to pay feature. This error occurs during connection.

Request

• Insights on the specific causes of this error and how to prevent it.
• Additional troubleshooting steps or solutions.

Thank you for looking into this issue. Any assistance in resolving this would be greatly appreciated.

[AnshulMindbody]

@bric-stripe Any comments?

[bric-stripe]

Hi, this happens when the Apple ProximityReader fails with prepareFailed during the connection process. That error provides an additional string that is exposed via the SCPErrorKeyPrepareFailedReason in the error's user info dictionary.

I checked some logs from what I assume is your app id¹ and all the failures I see are the same: "Reader error during attestation -2023". I'm checking with the team if we have, or can get, any more info on what explains this.

From spot checking some logs from devices that hit this it seems subsequent attempts end up succeeding. Does that match what you're seeing though? Or are you getting reports of users stuck receiving this error and unable to connect?

Footnotes

1. assumption based on your gh user name ↩

[Roniy08]

Hi, this happens when the Apple ProximityReader fails with prepareFailed during the connection process. That error provides an additional string that is exposed via the SCPErrorKeyPrepareFailedReason in the error's user info dictionary.

I checked some logs from what I assume is your app id1 and all the failures I see are the same: "Reader error during attestation -2023". I'm checking with the team if we have, or can get, any more info on what explains this.

From spot checking some logs from devices that hit this it seems subsequent attempts end up succeeding. Does that match what you're seeing though? Or are you getting reports of users stuck receiving this error and unable to connect?

Footnotes

1. assumption based on your gh user name ↩

did you have any solution for this connection issue? let us know if you can provide another way to resolve this