We had noticed “paymentCredentialsAvailable” is getting returned more from apple pay capabilities for some unexpected devices (our example is windows + chrome). Based off the documentation this should only be returning if this is linked to a wallet account w/ valid payment. From some investigation this appears to have changed from apple pay js v1.3.7 to v1.3.8 (latest). Previously the above windows + chrome example would return “paymentCredentialStatusUnknown” which is what would be expected in this case. Tried running chrome in icognito mode and clearing cookies just in case this check had some linkage to the apple account via QR code usage, but did not appear to affect the returned response. Unsure if this is a bug or a change to the logic, but doesn’t appear to be appropriately reflected in the documentation, also a change like this should not be appearing in a patch version. Has anyone else experienced this?
ApplePay JS v1.3.8 ApplePayCapabilities.PaymentCredentialStatus change?
Hi @Dwight55,
You wrote:
[...] Unsure if this is a bug or a change to the logic, but doesn’t appear to be appropriately reflected in the documentation, also a change like this should not be appearing in a patch version. Has anyone else experienced this?
I'll investigate this with the Apple Pay engineering and product team directly. However, I suggest for you to file a bug report via Feedback Assistant so we can learn more about your environment.
Please ensure your report includes the following details:
- Specific reproduction steps
- System platform and version
- Web browser name and version
Once your report is submitted, please reply here with the Feedback ID.
As a workaround until we determine the answer to your questions, you could temporarily pin the prior version (v1.3.7), if applicable.
Cheers,
Paris X Pinkney | WWDR | DTS Engineer
Thanks I’ll submit that to the feedback assistant. We did end up pinning to v1.3.7 for the time being.