Error during In-App Provisioning (eligibility step, PKErrorHTTPResponseStatusCodeKey=500)

Hi @dev-D-S,

You wrote:

Feedback Assistant ID: FB22007923 (Error during the In-App Provisioning process)

The error is due to an invalid nonce value. The nonce value contained within the encrypted card data must be identical to the nonce value provided to the add payment pass request.

Cheers,

Paris X Pinkney |  WWDR | DTS Engineer

Hi @dev-D-S and @DTS Engineer,

We were experiencing the same issue, have added the identical nonce and nonceSignature to the encrypted card data, but continue to receive the error:

ProvisioningOperationComposer: Step 'eligibility' failed with error <PKProvisioningError: severity: 'terminal'; internalDebugDescriptions: '(
    "eligibility request failure",
    "Received HTTP 500"
)'; underlyingError: 'Error Domain=PKPaymentWebServiceErrorDomain Code=0 "Unexpected error." UserInfo={PKErrorHTTPResponseStatusCodeKey=500, NSLocalizedDescription=Unexpected error.}'; userInfo: '{
    PKErrorHTTPResponseStatusCodeKey = 500;
}'; >

@DTS Engineer

Thank you so much for your reply.

Could you please share the nonce that was initially provided to the "add payment pass request", as well as the nonce included in the encrypted card data? Our provider insists that everything is functioning correctly on their side, so we’d like to review and compare the logs from all parties to better understand where the discrepancy might have occurred.

Would it be possible for you to provide this information?

Hi @csdevfr , Thank you for sharing this. If you manage to resolve it, please share the solution here as well; it would be very helpful.

By the way, I’m very sorry for spamming replies. The website wasn’t working properly and kept returning an error when I tried to post, so I didn’t realize my messages were actually going through.

@dev-D-S

I seem to be encountering the same posting error, to be safe, adding a new comment (not a reply to your prior):

I found this post: https://developer.apple.com/forums/thread/762893 and have created a feedback assistance request as mentioned. I did include all details, including the sysdiagnose log file.

If you haven't yet, I strongly recommend following the instructions on gathering those extra details via sysdiagnose.

@csdevfr Thank you for the recommendation.
My initial message included a link to the report with the sysdiagnose.

For context, here are my current setup:
• TestFlight builds.
• Production cards.
• Apple certification stage - the step where you need to select a lab for certification.

Our card provider insists that the encryption API is working as expected and that their SDK relies on the same implementation. Unfortunately, they haven’t been very responsive.

I’m hoping to receive the nonces from Apple so we can confirm whether the issue is on their side and have clear evidence to ask them to thoroughly verify everything.