You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Dec 16, 2023. It is now read-only.
In my case it highlighted "TeamIdentifer in signature matches value in pass.json" as problematic.
So I dug into PKPassValidator's source to figure out how that flag came to be. It's saying my template's teamIdentifier doesn't match up with the signature, specifically the OU field.
I opened up the certificate in my keychain and under the subject being certified, it listed Organizational Unit as WLJTXXXXXX. Copied that value into the source code (passed as an argument to createTemplate) and now the passes load correctly.
Hope this helps someone.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Hi, I wasted half a day on this problem and found a solution that I want to share since I assume this project is unmaintained.
If you could generate the pkpass with the library but macOS/iOS refuses to load the pass, use PKPassValidator to figure out what's wrong:
https://pkpassvalidator.azurewebsites.net
In my case it highlighted "TeamIdentifer in signature matches value in pass.json" as problematic.
So I dug into PKPassValidator's source to figure out how that flag came to be. It's saying my template's
teamIdentifier
doesn't match up with the signature, specifically theOU
field.I opened up the certificate in my keychain and under the subject being certified, it listed Organizational Unit as WLJTXXXXXX. Copied that value into the source code (passed as an argument to
createTemplate
) and now the passes load correctly.Hope this helps someone.
The text was updated successfully, but these errors were encountered: